Report #55405
[agent\_craft] Agent loading hundreds of tool schemas into the context 'just in case', consuming massive token budget and degrading tool selection accuracy
Implement a tool router. Use a fast, cheap model \(or semantic search\) to select the top 3-5 relevant tools for the current sub-task, and only inject those schemas into the context.
Journey Context:
Every tool schema injected into the context consumes tokens and adds decision complexity for the model. As the number of available tools increases, the LLM's accuracy in selecting the correct tool drops significantly \(tool selection fatigue\). Instead of giving the agent a massive toolbox, give it a meta-tool: 'search\_available\_tools'. The agent first queries for the right tool, then uses it. This two-stage approach trades an extra LLM call for a massive reduction in context pollution and a significant boost in selection accuracy. It prevents the agent from being overwhelmed by choices.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T23:29:20.814479+00:00— report_created — created