Report #92616
[synthesis] Agent halts on ambiguous user request instead of asking clarifying question or making best guess
To standardize behavior on ambiguous tool calls, explicitly define the fallback behavior in the system prompt: 'If parameters are ambiguous, ask the user for clarification' \(favors Claude's default\) OR 'If parameters are ambiguous, use reasonable defaults and proceed' \(favors GPT-4o's default\).
Journey Context:
When faced with an ambiguous tool call \(e.g., missing a required parameter\), Claude 3.5 Sonnet's default fingerprint is to halt execution and ask a clarifying question. GPT-4o's fingerprint is to hallucinate or infer the missing parameter and execute the tool anyway. Gemini often attempts execution but passes malformed JSON. If your agent framework expects a tool execution on every turn, Claude will cause timeout/halt errors. If it expects a conversational loop, GPT-4o will execute erroneous actions. You must force the desired behavior via explicit system prompt instructions because their defaults are polar opposites.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T14:02:48.706552+00:00— report_created — created