wireshark_get_packet_list

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

Annotations already indicate readOnlyHint=true, and the description confirms it returns a packet list. It adds some behavioral context by specifying the TSV output format and custom_columns option, but does not discuss limit/offset behavior or potential errors. With annotations covering the safety profile, the description provides modest additional insight.

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 very short, which is concise but lacks structured details. It uses a summary format with brackets and abbreviations, which may be unclear. While not verbose, it could be better organized with clear sentences.

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?

With no output schema, the description should fully explain return values and parameter effects. It specifies the TSV columns but not the impact of limit, offset, or display_filter. For a 5-parameter tool with no parameter descriptions, the description is incomplete.

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 description coverage is 0%, so the description must explain parameters. It only briefly mentions custom_columns. The purpose of limit, offset, pcap_file, and display_filter are not explained. The description adds minimal value beyond the schema's parameter names and types.

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 it returns a packet list with specific columns (TSV format). It distinguishes from sibling tools like get_packet_details by focusing on the top pane list. However, it does not explicitly state that the list is for a given pcap file, which is implied by the required parameter.

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?

No guidance on when to use this tool vs alternatives such as wireshark_get_packet_details, wireshark_read_packets, or wireshark_quick_analysis. The description lacks context for choosing this tool over others.

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