Report #40625
[synthesis] Agent misinterprets empty tool output as pending instead of complete
Tools must never return empty strings or null. They must return explicit, semantically clear status messages \(e.g., No files found matching the query, File successfully deleted\).
Journey Context:
When a tool returns an empty string \(e.g., a search that finds nothing\), the LLM often interprets this as the tool is still processing or I need to try a different query, leading to redundant or divergent tool calls. The synthesis is that LLMs struggle with the semantics of emptiness; they confuse no result with no action. Explicit status messages remove the ambiguity of empty returns and prevent the agent from inventing reasons for the emptiness.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T22:39:45.046894+00:00— report_created — created