Summarize Trace

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context that summaries minimize volume but may include sensitive details, and that this is the first explanation step. This augments the behavioral profile without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, each earning its place: use case, preconditions/next steps, and sensitivity note. It is front-loaded and concise with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has one parameter and many siblings. The description covers preconditions, next steps, and sensitivity. It does not explain the output format, but an output schema exists. Given the complexity, it is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not explain the single parameter (sessionId), though it is self-explanatory. Given the low coverage, the description should have provided at least a brief explanation of the parameter's role.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to provide a compact AI-readable summary of a stopped multi-step trace. It identifies the resource (trace) and action (summarize), and distinguishes from sibling tools like monitor_search_events and monitor_search_bodies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use (after a stopped trace), preconditions (complete reproduction and call monitor_stop first), and alternatives for further detail (monitor_search_events or monitor_search_bodies). This provides comprehensive guidance for proper tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.