wireshark_get_packet_bytes

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

No annotations provided, so description carries full burden. States it returns raw dump like Wireshark's pane, implying read-only, but does not explicitly disclose non-destructive nature or any potential side effects. Adequate but not thorough.

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?

Extremely concise with one-line purpose, clear Args/Returns sections, and an example. No redundant text, 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?

Given the tool's simplicity (2 required params, read operation), the description is largely complete. Output schema exists but is not described; however, the return type is implied. Could mention the output format explicitly, but effective for basic use.

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 has 0% description coverage. Description lists 'pcap_file: Path to capture file' and 'frame_number: The packet number', adding basic meaning beyond type names. Could specify formats or constraints, but provides minimal useful context.

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 specifies 'Get raw Hex/ASCII dump' and references Wireshark's Packet Bytes pane, clarifying the verb and resource. It distinguishes from siblings like wireshark_get_packet_details which provide parsed details, but the purpose is clear.

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 versus alternatives like wireshark_get_packet_details or wireshark_follow_stream. Does not mention when-not-to-use or provide context for selection.

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