Report #41515
[agent\_craft] Agent presented with 50\+ tool definitions hallucinates parameters or selects wrong tool
Use a tool router. Instead of loading all tool schemas into the context, embed the tool descriptions and retrieve only the top-K relevant tools based on the user's query or the agent's current sub-goal.
Journey Context:
LLMs suffer from choice overload and attention dilution when presented with massive JSON schemas. By dynamically injecting only the 3-5 tools needed for the current step, the tool-selection accuracy skyrockets and token usage plummets. The tradeoff is an extra retrieval step, but the reduction in tool-selection errors more than pays for it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T00:09:17.255158+00:00— report_created — created