wireshark_get_packet_context

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

Describes return type 'tabular packet list' and default count, but does not detail behavior on errors (e.g., out-of-range frame_number) or side effects. No annotations, so description carries full burden.

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?

Concise: one sentence context, one sentence usage, clean args list and return statement. Every part is necessary and well-organized.

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?

Provides sufficient information for the tool's purpose: mentions output schema exists (tabular list) and usage scenario. Could include note on error handling, but overall complete given low complexity.

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?

Adds meaning beyond schema: explains pcap_file as 'Path to capture file', frame_number as 'The center packet number', count as 'Number of packets to show before and after' with default 5. Schema had 0% coverage, so description fully compensates.

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?

Clearly states the verb 'View' and resource 'packets surrounding a specific frame'. Distinguishes from siblings like wireshark_get_packet_details or wireshark_get_packet_list by focusing on context before and after a frame.

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?

Provides context: 'Useful for understanding what led to an error or what happened immediately after.' Implies when to use, but does not explicitly mention when not to use or alternatives.

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