Report #103825
[tooling] LLM calls the wrong MCP tool or ignores optional parameters
Write tool descriptions as if they were part of the system prompt: open with exactly when to call the tool, describe each parameter's role and valid values inline, and include one or two minimal example calls for non-obvious tools.
Journey Context:
The model only sees the tool name, description, and parameter schema. Vague descriptions like 'Search the codebase' cause the model to misuse the tool or omit important arguments. Empirically, descriptions that state the trigger condition \('Use this when the user asks about X'\) and enumerate enum values in plain language reduce incorrect invocations more than adding more tools. Parameter descriptions matter as much as the top-level description.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-13T04:46:18.864841+00:00— report_created — created