get_pcap

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

Discloses saves to disk, returns only metadata, format differences per backend, and security warning (untrusted data). Without annotations, it covers key behavioral traits well, though could mention if operation is safe/destructive.

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?

Four well-structured sentences, each adding value. Purpose first, then behavioral details, returns info, and security. No redundancy or waste.

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?

Covers essential aspects: purpose, behavior, format differences, security. With output schema present, return values are handled. Could mention permissions or error cases but minimal gaps.

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 100% with clear description for task_id. Tool description reiterates the schema's format but adds no new semantics beyond baseline.

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 downloads PCAP for finished detentions, with verb and resource. It distinguishes from sibling tools like download_sample and get_report by specifying network traffic capture and condition.

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?

Implies usage after detonation is finished and specifies task_id format, but lacks explicit guidance on when not to use or alternatives. The security warning is helpful but doesn't fully clarify usage context.

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