A task needs many more model calls than expected. What do you examine?
Why A is the answer
The trace, for loops and repeated steps
Traces show repeated or wasted steps.
In detail
- Traces show loops and repeated steps.
- Traces show repeated steps.
Use case
An illustrative scenario, not a real incident.
A task uses 60 calls, and the trace shows a loop on one search.
See it in different ways
flowchart LR A["Agent run"] --> B["Trace of each step"] B --> C["Dashboards and alerts"] C --> D["Root cause"] D --> E["Add a test and fix"]
stateDiagram-v2 [*] --> Running Running --> Incident Incident --> ReadTrace ReadTrace --> Fix Fix --> AddEvalCase AddEvalCase --> StagedRollout StagedRollout --> Running
flowchart LR S0["Open the trace"] --> S1["Find repeats"] --> S2["Fix the loop"]
Key point: Traces reveal waste.
Why the other options are wrong
- B. The tokenizer's vocabulary size
- Vocabulary is unrelated.
- C. The model card's release date
- A release date is unrelated.
- D. The model's release notes
- Release notes do not show your runs.