Report #16056
[gotcha] LLM ignores or misuses MCP tools with empty or generic descriptions
Write highly specific, action-oriented descriptions for every tool and its properties. Include examples of when to use the tool and when \*not\* to use it.
Journey Context:
Because MCP tool schemas are just JSON Schema, developers often leave the \`description\` field blank or write a single word \(e.g., 'Search'\). The LLM relies entirely on the description to differentiate between tools. If two tools have similar names but sparse descriptions, the LLM will guess, leading to incorrect tool selection. The description is the LLM's search index; it must be rich.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T01:45:27.283876+00:00— report_created — created