analyze_large_pcap

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds key behavioral details: chunked processing, progress reporting via ctx, and optional display filter. However, it does not disclose what statistics are accumulated or output format.

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 concise and front-loaded with the main purpose, but includes an 'Args' section that largely repeats schema information, slightly reducing efficiency.

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 lacks details about return values or output, which is significant given no output schema. It mentions 'accumulating statistics' but not what statistics or how they are returned, leaving an information gap.

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 adds some meaning to parameters (e.g., filepath is a path, chunk_size is packets per chunk, display_filter is optional Wireshark filter) and introduces ctx (MCP context) not in schema, partially compensating for schema gaps.

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 analyzes large PCAP files in chunks for memory efficiency, differentiating it from similar tools like analyze_pcap_file by emphasizing chunked processing for large files.

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 implies use for large files ('for memory efficiency') but does not explicitly state when to use this tool versus siblings like analyze_pcap_file, analyze_dns_traffic, etc., nor does it provide exclusions or alternatives.

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