Report #88210
[synthesis] Hallucinations and crashes from empty or null tool return values
Never return empty strings, null, or void tool results. Always return a structured JSON with at least a \`status: "success"\` or a brief summary string \(e.g., 'File written successfully'\).
Journey Context:
A common pattern in coding agents is to return nothing on success. LLMs handle this terribly. GPT-4o often hallucinates a summary of what it thinks the tool did \(which can mislead subsequent steps\). Claude 3.5 tends to error out or get confused, asking to retry the tool. Gemini might just output 'Done.' without formatting. Returning explicit confirmation prevents hallucinated tool outputs and loop crashes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:38:46.748023+00:00— report_created — created