Principle
Measure the active tool set, not the catalog size
The catalog is inventory. The working set is cognitive load.
Before you use it
- Use when
- A team argues about how many tools an agent can support but does not know how much tool context each request actually sees.
Keep this limit in mind
- Do not optimize the working set in isolation. Extra routing steps or low recall can erase the savings.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Track the count and token footprint of tool schemas active per request, alongside tool-selection accuracy and task success. A large catalog can be acceptable if the working set remains relevant; a small catalog can still be wasteful if every verbose schema is always loaded.
An example
Two agents both expose 80 available tools. One routinely shows six relevant schemas; the other shows all 80. Catalog size alone hides the meaningful difference.
Check your result
Tool-context changes are evaluated with working-set size and task outcomes rather than only total tools registered.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
More from this collection
Operate AI agents as systems you can replay, verify and constrain
Retrieve code before sending codeTurn repeated browser work into persistent programsEvidence and sources
The active number and size of tool schemas presented to the model can be measured separately from the total catalog to diagnose context and selection overhead.
A smaller working set is not automatically better; over-pruning can reduce task coverage or force extra routing turns.
The 100-Tool Agent Is a Trap: Scaling with Semantic Routers and JIT Context · 12:47-20:22, measure the working set and connect retrieval to evaluation and maintenance
Edition and review
Version 0.1.0
No review details are supplied for this edition.