wireshark_read_packets

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

The description adds deprecation context, but no other behavioral details beyond what annotations (readOnlyHint=true) already convey. It does not contradict annotations.

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 concise with a single sentence and starts with the key 'DEPRECATED' flag, but it could include a brief note on what 'JSON packet data' means.

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?

While deprecation is flagged, the description is too minimal for a tool with 4 parameters and no output schema; agents lack context on return format or how to use parameters if they attempt to use it.

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 mentions no parameters, and schema coverage is 0%, leaving the agent to rely solely on parameter names and types without any semantic guidance.

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 provides 'JSON packet data' and marks it as deprecated, which identifies its purpose despite lacking specificity about the data source or structure.

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?

Explicitly tells the agent to use 'get_packet_list + get_packet_details instead', offering clear guidance on alternatives and when not to use this tool.

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