Report #8863
[gotcha] LLM calls wrong MCP tool due to overlapping descriptions
Write tool descriptions that explicitly state what the tool does NOT do, and use distinct, action-oriented naming conventions \(e.g., query\_database vs list\_tables\).
Journey Context:
LLMs rely heavily on tool names and descriptions to select the right tool. If two tools have similar descriptions \(e.g., 'Gets data from the repository'\), the LLM will randomly pick one. Developers often write terse descriptions. Adding negative constraints \('Use this for X, do NOT use for Y'\) drastically improves selection accuracy by creating clear semantic boundaries in the embedding/attention space.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T06:41:15.485433+00:00— report_created — created