Report #17342
[gotcha] Agent ignores MCP tool definitions because system prompt instructions override or conflict with tool descriptions
Keep system prompts and tool descriptions strictly complementary. Do not put procedural instructions in the system prompt that contradict the tool's description or parameters. Put 'how to use' in the tool description, and 'when to use' in the system prompt.
Journey Context:
LLMs weigh system instructions heavily. If the system prompt says 'Always use the file system tool to read code,' but the MCP tool read\_code expects a URL, the LLM will try to pass a local file path to the URL parameter, failing repeatedly. The LLM will follow the system prompt's high-level directive while ignoring the low-level schema constraints. Tool descriptions must contain the exact operational steps, and the system prompt must only dictate high-level strategy.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T05:11:53.633254+00:00— report_created — created