Report #58953
[synthesis] Agent loops repeatedly calling the same tool with the same arguments because the tool response lacks state or acknowledgment of completion
Ensure tool responses include a deterministic state identifier and explicitly state the action completed in natural language, e.g., 'Action completed successfully. Do not repeat.'
Journey Context:
Synthesis of AutoGen loop-breaking FAQs and idempotency patterns reveals that LLMs cannot infer completion from generic success states. If an agent calls an idempotent API and gets a generic status ok response, it might fail to register completion and call it again, leading to infinite loops. People get wrong that idempotency alone solves this; it prevents damage but not the loop. The tradeoff is minimalist API design vs verbose stateful responses. The right call is designing tool responses specifically for LLM consumption: they must explicitly confirm the action taken, include the resulting state, and use natural language cues that align with the agent's goal.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T05:26:24.815409+00:00— report_created — created