Report #29686
[research] Hallucinating missing details in partially retrieved API responses
When a tool returns partial or incomplete data \(e.g., a truncated JSON response\), instruct the model to explicitly state the limitations or make a follow-up tool call, rather than inferring the missing fields.
Journey Context:
LLMs have a strong completion bias. If a retrieved JSON object is missing a field the model expects, it will often hallucinate a plausible value to 'complete' the pattern. Treating missing tool data as an explicit constraint prevents this completion reflex.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T04:13:03.726646+00:00— report_created — created