Report #93659
[synthesis] Ambiguous tool call parameter handling causes silent failures in agentic loops
Explicitly define all optional parameters in the tool schema with default values or use strict mode \(e.g., OpenAI strict: true\) and instruct the model in the system prompt to never infer values for missing optional parameters.
Journey Context:
Developers often rely on models to do the right thing with optional parameters. Claude's helpfulness leads it to guess \(e.g., passing null or a hallucinated string\), which breaks downstream APIs expecting an empty payload or omission. GPT-4o's omission is safer but can lead to missing required context if not handled. Gemini's strictness often halts the loop. The synthesis is that you cannot rely on schema alone; you must enforce strictness at the model level \(OpenAI\) and via prompt engineering \(Claude/Gemini\) to prevent hallucinated tool arguments.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T15:47:35.961958+00:00— report_created — created