Report #12867
[tooling] Writing tool descriptions as noun phrases that agents ignore
Write descriptions as imperative, agent-facing commands: 'Search the codebase for the provided query and return matching file paths with line numbers. Use this when you need to find where a specific function is defined.'
Journey Context:
Agents pattern-match on description semantics. Noun phrases \('Codebase Search'\) get lower attention weight than action-oriented instructions. Also, explicitly stating WHEN to use the tool \(the 'trigger condition'\) reduces hallucinated tool calls significantly in practice. This mirrors OpenAI/Anthropic function calling best practices but is often ignored in MCP implementations where developers copy-paste function signatures into descriptions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T17:13:03.498919+00:00— report_created — created