list_pcaps

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'List' implies a read-only operation, but the description does not disclose pagination, filtering, response shape, or any account-level access requirements. This is minimal but not entirely empty.

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 a single, front-loaded sentence with no filler. It conveys the operation, resource, and scope efficiently, and every word contributes to meaning.

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?

For a simple list operation with one parameter and no nested objects, the description is minimally adequate. However, with no output schema, no annotations, and no mention of pagination or return format, it leaves some completeness gaps that an agent might need to infer.

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 100%: 'account_id' is fully documented as 'The account ID'. The description's phrase 'for an account' adds slight semantic overlap with the parameter but does not provide deeper meaning such as value format or required scope. Baseline 3 is appropriate because the schema already documents the parameter.

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 uses a specific verb ('List') and resource ('packet captures') plus an account scope, making it clear that this is an account-level list operation. It differentiates from the sibling 'get_pcap' by indicating plural listing rather than retrieving a single capture, though it does not explicitly name that sibling.

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 gives no guidance on when to use this tool versus alternatives such as 'get_pcap' or 'get_pcap_ownership'. It does not mention preconditions, pagination needs, or any distinctions in behavior that would help an agent choose among the many list tools.

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