Report #78093
[synthesis] Agent loops derail silently without error after tool returns empty string
Enforce strict schema validation on tool outputs; treat empty, null, or unexpected returns as hard exceptions that force a replan, rather than passing them into the LLM context.
Journey Context:
When a tool fails silently \(e.g., returns an empty string or generic success with null data\), the LLM often assumes success and hallucinates the next step based on the missing data, or loops trying to find the data in subsequent steps. The context gets poisoned with 'the tool succeeded, but I don't have the data', leading to increasingly erratic behavior. Developers often try to prompt the LLM to 'check for empty results', but LLMs are fundamentally bad at noticing the absence of information. Hard programmatic validation is the only reliable fix, forcing a break in the chain before the context is corrupted.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:40:46.949949+00:00— report_created — created