Report #84225
[synthesis] Tool calls fail or execute dangerously when required parameters are ambiguous in the prompt
Implement a pre-execution validation layer. If a required parameter is missing, intercept the call: for GPT-4o, return an API error message; for Claude, return a specific 'Ask user' tool call; for Gemini, reject and re-prompt.
Journey Context:
Faced with missing parameters, GPT-4o often omits the parameter or passes null, leading to downstream API crashes. Claude 3.5 tends to hallucinate a plausible value \(e.g., guessing a default file path\) to maintain conversational flow. Gemini often throws an API-level INVALID\_ARGUMENT. Assuming models will just ask the user is wrong. The synthesis reveals a tri-modal failure: GPT-4o fails silently, Claude acts dangerously, Gemini fails loudly. A validation middleware is the only safe cross-model fix.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T23:57:57.951400+00:00— report_created — created