# Track tool errors, tool calls, runtime and tokens as agent diagnostics

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Track tool errors, tool calls, runtime and tokens as agent diagnostics

ID: MHC-D-RESEARCH-0958 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/track-tool-errors-tool-calls-runtime-and-tokens-as-agent-diagnostics

The path to the answer reveals inefficiency before users notice the bill or latency.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Agent evaluation records only final pass/fail.

### Avoid when

- Lower cost or fewer calls are not automatically better if they reduce robustness or coverage.

### Explanation

Alongside task success, record number of tool calls, tool errors, runtime, token use and repeated calls. These metrics help detect confused tool selection, bloated responses, loops and regressions that final accuracy can hide.

### Checklist

- Count tool calls by tool.
- Count validation/tool errors.
- Track total runtime and major tool latency.
- Track token/context consumption.
- Flag repeated or redundant calls on successful tasks too.

### Example

Two agents both pass, but one needs 7 tool calls and the other 48 with five schema errors; that difference deserves investigation.

### Check

Efficiency and failure-path regressions are visible even when final success stays constant.

### Limits

- Lower cost or fewer calls are not automatically better if they reduce robustness or coverage.

### Evidence and sources

- supports: Anthropic recommends tracking runtime, tool-call count, token consumption and tool errors in addition to top-level accuracy. — RS-6E5D62426C731E4C. Lower cost or fewer calls are not automatically better if they reduce robustness or coverage. (See source record)
- RS-6E5D62426C731E4C: Writing effective tools for AI agents—using AI agents — https://www.anthropic.com/engineering/writing-tools-for-agents

No review details supplied.
