list_tcp_streams

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds no additional behavioral context such as output format, pagination, or limitations. It does not contradict annotations, but adds minimal value beyond them.

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 concise with two meaningful sentences. It is front-loaded with the core purpose. However, the 'Args' section is redundant given the schema, which slightly reduces efficiency.

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 (one parameter, no output schema), the description covers the basic functionality but lacks hints about what the output looks like (e.g., list of stream numbers or details). Annotations help, but the description could be more complete.

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 includes an 'Args' section that says 'filepath: Path to PCAP/PCAPNG file', which essentially repeats the schema's title 'Filepath' with a generic description. With 0% schema description coverage, the description does not provide additional meaning like file size limits or supported paths.

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 verb 'list' and resource 'TCP conversations' with the condition 'found in a PCAP file'. It is specific and distinct from siblings like 'follow_tcp_stream' which focuses on a single 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?

The description implies usage when listing TCP streams from a PCAP file but does not provide explicit guidance on when to use versus alternatives like 'follow_tcp_stream' or other analysis tools. No when-not or alternative hints are given.

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