Report #72269
[gotcha] Agent selects wrong tool or hallucinates tool names with 30\+ registered tools
Cap actively exposed tools to 10-15 at a time. Group tools by domain and use a router/tool-discovery pattern: a top-level tool that returns the relevant sub-tools for a given task category. Validate that tool names are distinct and descriptions are unambiguous.
Journey Context:
LLM tool selection follows a recall-over-precision curve. With few tools, the model reliably picks the right one. Beyond ~15-20 tools, selection accuracy drops noticeably — the model confuses similarly-named tools, ignores better-suited tools, or hallucinates tool names that don't exist. This isn't a bug in the model; it's a fundamental attention limitation over long tool lists. The common mistake is registering every available MCP tool globally. The fix is architectural: a tool router or categorization layer that narrows the active tool set per request. Some frameworks implement this as 'tool namespaces' or 'skill groups.'
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T03:53:00.920375+00:00— report_created — created