slice_pcap

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

Annotations already indicate idempotent and non-destructive behavior. The description adds minimal extra context (e.g., 'uses editcap'), but does not elaborate on file creation or requirements for permissions. Given annotations, the description is adequate but provides little beyond the structured data.

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 front-loaded with the main purpose and then lists parameters concisely. Each parameter description is brief but informative. No superfluous text, though the parameter list is necessary given the number of parameters.

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 description explains all parameters but does not mention what the tool returns or how to handle errors. Since there is no output schema, some explanation of output format or side effects would improve completeness. Still, the parameter descriptions are thorough.

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?

With 0% schema description coverage, the description compensates by listing each parameter and its meaning in the Args section (e.g., start_packet: first packet number to keep, start_time: keep packets after this time). This adds significant value beyond the bare schema.

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 'Slice or filter a PCAP file using editcap,' specifying the action (slice/filter) and resource (PCAP file). It effectively distinguishes the tool from siblings like merge_pcap_files or convert_pcap_format.

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 provides no guidance on when to use this tool versus alternatives such as merge_pcap_files, analyze_pcap_file, or convert_pcap_format. There is no when-to-use or when-not-to-use information.

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