Export Trace Bundle

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

Annotations (readOnlyHint=false, destructiveHint=false) indicate it's a write operation but not destructive. The description adds critical context: the ZIP can contain all captured secrets, bodies, cookies, DOM, screenshots, and WebSocket frames, plus requires a protected destination. This goes well beyond annotations and warns of high sensitivity.

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 four sentences and front-loads purpose. It is concise but could be better structured (e.g., bullet points for preconditions). Still, every sentence adds value.

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?

Given the presence of an output schema (return values not needed), the description adequately covers purpose, preconditions, sensitivity, and post-export actions. However, with 0% schema parameter coverage, the omission of sessionId leaves a completeness gap for a tool with 3 parameters.

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 coverage is 0% (no descriptions in schema). The description mentions 'ZIP' (matching format) and 'protected local path' (related to outputPath) but does not explain sessionId or parameter details. With 3 undocumented parameters, the description should provide more guidance.

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 exports a ZIP of a completed trace for authorized handoff or offline analysis. It uses specific verb ('export'), resource ('trace bundle'), and format ('ZIP'), distinguishing it from sibling monitor tools that start/stop recording or list sessions.

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 specifies when to use ('authorized handoff or offline analysis'), preconditions (trace session must exist, protected local path), and next steps (share via approved channel, remove after use). It lacks explicit alternatives but the context is clear enough for an agent to decide.

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