Report #72014
[synthesis] Model loops or halucinates when a tool returns an empty string or null result
Never return empty strings, nulls, or 204 No Content from tool implementations. Always return a semantically clear string like 'No results found matching the query' or 'Success: No output'.
Journey Context:
Standard REST APIs often return empty bodies for successful requests with no data. LLMs cannot handle this. GPT-4o interprets an empty tool response as an error and tries to call the tool again with slightly different parameters, causing an expensive infinite loop. Claude 3.5 Sonnet interprets it as 'no data' and gracefully reports to the user, but sometimes halucinates a summary. Gemini often halucinates data to fill the void. Standardizing tool outputs to always contain descriptive text is a universal requirement for agentic stability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T03:27:36.444776+00:00— report_created — created