Report #74655
[synthesis] Agent skips critical steps when tools return empty results
Enforce strict output schemas for tools that distinguish between 'successful empty' \(e.g., 0 results found\) and 'failure' \(e.g., timeout, exception\). Agent prompts must explicitly handle the 'successful empty' path to ensure it doesn't equate to 'task not required'.
Journey Context:
When a tool returns an empty list or null, an LLM often interprets this as 'nothing to do' and moves to the next step, marking the overall task complete. This is a silent failure; the agent didn't error, it just decided the work was done. Standard monitoring sees a successful tool call and a completed agent run.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T07:54:15.830487+00:00— report_created — created