Report #90552
[synthesis] Missing required tool parameter causes hallucinated defaults vs clarification loops across models
Explicitly define a null or empty string default in the JSON schema and add an instruction: 'If a required parameter is not provided in the context, pass null and do not ask the user for clarification.'
Journey Context:
When context lacks a required tool parameter, GPT-4o tends to hallucinate plausible values to fulfill the schema, Claude 3.5 Sonnet often initiates a clarification loop \(calling a non-existent ask\_user tool or just chatting\), and Gemini frequently returns an API error or empty string. This divergence breaks deterministic agent loops. Forcing a null default standardizes the behavior, shifting the handling logic to the agent executor rather than relying on unpredictable model-specific guessing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T10:35:17.495712+00:00— report_created — created