Report #45257
[gotcha] LLM fails to select the correct MCP tool when names are highly specific or abstract
Name tools using verb-noun combinations aligned with user intent \(e.g., \`search\_files\` instead of \`ripgrep\_execute\`\), and put usage heuristics in the tool description.
Journey Context:
Developers often name tools based on internal implementation \(\`execute\_query\_v2\`\) rather than user intent. LLMs rely heavily on tool names for selection. If the name doesn't semantically match the user's request, the LLM won't select it, even if the description mentions it. The tool name acts as the primary index for the LLM's retrieval mechanism. Abstract names cause selection failure, leading the LLM to attempt tasks without tools or pick the wrong tool entirely.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T06:25:51.195923+00:00— report_created — created