An agent keeps repeating tools without making progress. How would you diagnose it?

Uses traces to separate unclear goals, bad tool interfaces, missing state, contradictory results, poor termination, and retry amplification.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I stop or isolate the run, then inspect the full trajectory: goal, instructions, eligible tools, calls and arguments, results, plan changes, progress markers, and termination checks. I look for identical calls, equivalent calls with rewritten arguments, errors returned as success, missing observations, and state that was never persisted. The immediate safeguard is a repetition and no-progress limit.

Full answer below

Practice focus

Agent debugging, trajectory analysis, loop detection, tool contracts, and durable correction.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Repeated calls are a symptom; the cause may be the agent, the tool, the state model, or the task contract.
I stop or isolate the run, then inspect the full trajectory: goal, instructions, eligible tools, calls and arguments, results, plan changes, progress markers, and termination checks. I look for identical calls, equivalent calls with rewritten arguments, errors returned as success, missing observations, and state that was never persisted. The immediate safeguard is a repetition and no-progress limit.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Common causes include overlapping tool descriptions, a tool result that omits the field needed for the next decision, stale context, an impossible completion criterion, blind retry, or a plan that forgets completed work. I reproduce the case with captured tool responses and compare it with successful trajectories. The fix targets the boundary: improve schemas, return typed errors, persist state, narrow tools, or make completion deterministic.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Increasing the maximum-turn limit.
Rewriting the prompt without inspecting tool results.
Assuming every repeated call is harmless.

An agent keeps repeating tools without making progress. How would you diagnose it?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next in path

Tech stacks

Skill areas

Human editorial direction

Was this drill useful?

Found this answer useful?