wireshark_analyze_suspicious_traffic

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

With no annotations, the description must disclose behaviors. It states 'comprehensive anomaly analysis' but lacks specifics on what analysis is performed, outputs, or side effects. No mention of performance impact or permissions.

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 short and includes section headers (Args, Returns, Example), which is good structure. However, it is too brief and lacks detail needed for effective use.

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 0% schema coverage and no annotations, the description is incomplete. It references an output schema but does not describe return values beyond 'comprehensive anomaly analysis', leaving ambiguity.

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%, so description should add meaning. It only says 'Path to capture file' for pcap_file, which is basic and adds little beyond the schema. For a single parameter, more context would help.

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 title and description clearly indicate security anomaly analysis, mentioning specific types like cleartext, unusual ports, and data volumes, which distinguishes it from sibling tools focused on specific threats (e.g., DNS tunnel, DoS).

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 like wireshark_security_audit or wireshark_check_threats. No explicit when-not-to-use instructions.

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