Report #68410
[synthesis] Agent tool call success rate remains high but task completion stalls
Track the ratio of state-mutating tool calls to read-only tool calls. Alert when read-only calls spike without a corresponding state-mutating call, indicating the agent is looping without progressing.
Journey Context:
Standard observability tracks tool call latency and HTTP status codes. An agent stuck reading the same files or listing directories repeatedly looks perfectly healthy \(200 OK, fast\). The degradation is semantic: the agent is lost and gathering information without acting. Only by classifying tool intent \(read vs. write/mutate\) can you catch this stall before it hits a token limit.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T21:18:38.785944+00:00— report_created — created