Report #74066
[agent\_craft] Agent is given dozens of tool schemas in the system prompt, causing it to hallucinate parameters or select the wrong tool because definitions blur together
Implement a tool router: only inject the schemas for the 3-5 tools relevant to the current sub-task into the immediate context, keeping the rest in a searchable tool registry.
Journey Context:
Every tool definition consumes tokens and adds cognitive load. Research on API-calling LLMs shows that tool-calling accuracy drops significantly as the number of available tools increases. A two-step process—first route to a relevant tool subset, then call the tool—drastically improves accuracy and reduces prompt cost compared to injecting all tools at once.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T06:54:58.158435+00:00— report_created — created