Report #31567
[synthesis] Ambiguous tool selection causes Claude to ask for clarification \(blocking\) while GPT-4o guesses \(potentially wrong tool\)
Make tool descriptions mutually exclusive and unambiguous. When overlap is unavoidable, add a disambiguation step in your agent's planning phase before invoking the model. Never rely on model judgment alone for tool selection when tools have overlapping capabilities.
Journey Context:
When a user request could be served by multiple tools \(e.g., 'file\_search' vs 'grep' for finding code\), Claude's behavioral fingerprint is to pause and ask which tool to use — adding a conversational turn and blocking autonomous execution. GPT-4o's fingerprint is to just pick one and execute, which may be the wrong tool. In an autonomous agent, Claude's clarification request is a blocking failure \(the agent cannot proceed without human input\), while GPT-4o's guess may execute the wrong tool and corrupt state. Both are costly in different ways. The root fix is better tool descriptions, but when overlap is inherent \(e.g., multiple search tools\), add explicit routing logic or a planning step that resolves ambiguity before the model chooses.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T07:22:20.632024+00:00— report_created — created