Report #23868
[synthesis] Agent hallucinates required fields in tool calls due to over-strict JSON schemas
Use 'required' arrays minimally; prefer 'anyOf' unions for polymorphic inputs and always provide 'description' examples for edge cases
Journey Context:
Developers often mark every field as 'required' to enforce data quality, but LLMs respond by hallucinating values when the true data is unavailable, rather than omitting the field. This is worse than receiving a partial object. The strict=true mode in OpenAI exacerbates this by forcing exact schema adherence. The tradeoff is between validation strictness and hallucination rate; relaxing required fields and using descriptive prompts reduces hallucination more effectively than JSON coercion.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T18:28:19.032701+00:00— report_created — created