wireshark_stats_io_graph

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

The description adds some behavioral context beyond annotations: it explains the output type (I/O Graph) and parameter semantics. Annotations already declare readOnlyHint=true, so the description is consistent but not exhaustive; it lacks details on return format or limitations.

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 two sentences, front-loading the purpose and then explaining parameters. Every sentence adds value; no wasted words.

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 the tool's moderate complexity, the description covers the purpose and key parameters. However, it lacks details on the output format and could better differentiate from sibling stats tools, though the type name helps.

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?

The description explains interval as 'bucket size in seconds' and filters as 'optional semicolon-separated display filters to break the traffic out by type', adding meaning to the schema which has 0% description coverage. However, pcap_file is not described beyond being required.

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 produces an I/O Graph showing traffic volume over time, which is a specific verb+resource. It distinguishes from sibling stats tools like wireshark_stats_protocol_hierarchy, wireshark_stats_endpoints, etc., by naming the output type.

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?

There is no guidance on when to use this tool versus alternatives like wireshark_stats_protocol_hierarchy or wireshark_stats_conversations. The description does not mention prerequisites or when not to use it.

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