wireshark_get_packet_list

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

No annotations exist, so description carries full burden. It describes the return format (tabular list with columns), pagination via limit/offset, filtering via display_filter, and customization via custom_columns. Behavior is well explained though no mention of performance or safety constraints.

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?

Well-structured with [Summary], Args, Returns, Example sections. Front-loaded with key purpose sentence. No redundant content; every sentence adds value.

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 tool with 5 parameters, no annotations, but with output schema, the description is complete: it explains parameter semantics, return structure, and customization. The example ties everything together.

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%, but description explains every parameter: pcap_file (path), limit (rows), offset (skip), display_filter (Wireshark filter), custom_columns (comma-separated fields). Provides an example call demonstrating usage, fully compensating for lack of schema descriptions.

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?

Description clearly states 'Get a summary list of packets (like Wireshark's top pane)', specifying the verb and resource. The phrase 'Use this first to scan traffic before drilling down' differentiates it from sibling tools like wireshark_get_packet_details or wireshark_follow_stream.

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?

Explicit advice to 'Use this first to scan traffic before drilling down' provides clear context for when to use. While alternative tools are not named, the description implies a workflow ordering and the sibling list provides context.

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