Report #78250
[agent\_craft] Router LLM fails to select the correct tool or context source because the tool descriptions are too vague or too similar
Write tool descriptions as distinct, mutually exclusive contracts. Include concrete examples of when to use and when not to use the tool in the description, and use a smaller, faster model for routing if the toolset is large.
Journey Context:
If tool descriptions overlap \(e.g., 'Search the codebase' vs 'Find files'\), the router will hallucinate or pick arbitrarily. The router needs clear decision boundaries. By adding negative examples \('Do not use this for finding specific code snippets, use the code search tool instead'\), the router's accuracy skyrockets. Furthermore, routing is a classification task; a small, fine-tuned model or even an embedding similarity search is often faster and more reliable than a massive generative model for this step.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:56:19.680529+00:00— report_created — created