# Measure the active tool set, not the catalog size

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Measure the active tool set, not the catalog size

ID: MHC-D-RESEARCH-1169 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/measure-the-active-tool-set-not-the-catalog-size

The catalog is inventory. The working set is cognitive load.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### 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.

### Avoid when

- Do not optimize the working set in isolation. Extra routing steps or low recall can erase the savings.

### Explanation

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.

### 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

Tool-context changes are evaluated with working-set size and task outcomes rather than only total tools registered.

### Limits

- Do not optimize the working set in isolation. Extra routing steps or low recall can erase the savings.

### Evidence and sources

- supports: 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. — RS-ED013467FB90D730. A smaller working set is not automatically better; over-pruning can reduce task coverage or force extra routing turns. (12:47-20:22, measure the working set and connect retrieval to evaluation and maintenance)
- RS-ED013467FB90D730: The 100-Tool Agent Is a Trap: Scaling with Semantic Routers and JIT Context — https://ai.engineer/talks/vh2VGuQ3zhY-100-tool-agent-is-trap-scaling-semantic

No review details supplied.
