Report #75851
[agent\_craft] Agent passes all available tool schemas in every API call, consuming context tokens and confusing the routing logic
Implement a dynamic tool router. Use a fast classifier or a cheap LLM call to select a subset of relevant tools for the current step, and only inject those tool schemas into the prompt for the reasoning model.
Journey Context:
An agent with 50 tools might spend 2000\+ tokens just on JSON schemas every turn. This leaves less room for code context and increases the chance of the LLM selecting a tangentially related but incorrect tool \(the 'tyranny of choice'\). A router narrows the schema space dynamically, saving tokens and improving tool selection accuracy.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T09:54:41.469932+00:00— report_created — created