list_tcp_conversations

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

With no annotations provided, the description carries the full transparency burden. 'Enumerate ... in a PCAP' implies a read-only listing operation and the metrics phrase explains what will be computed, but the description does not disclose ordering, side effects, file-handling constraints, or scaling limitations.

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 a single, front-loaded sentence containing the verb, object, input context, and emitted data with no filler or redundancy.

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?

For a one-parameter listing tool with an output schema available, the description is largely complete: it specifies the input, the granularity of the listing, and the metrics returned. It only lacks explicit guidance about relationship to sibling tools and operational caveats.

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 compensate for the file_path parameter. It does so by placing the operation 'in a PCAP', clarifying that file_path should point to a capture file. For a single self-named parameter, this is adequate, though path formats or constraints are not detailed.

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 uses a specific verb ('Enumerate'), a precise resource ('TCP conversations (4-tuple) in a PCAP'), and clarifies the output (packet/byte counts and timing). This clearly separates it from siblings like analyze_tcp_conversation, which implies a deeper per-conversation analysis.

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?

Usage context is implied: this tool is for producing an overview of all TCP conversations in a capture. However, it does not explicitly state when to prefer this over analyze_tcp_conversation or otherwise name alternatives and exclusion conditions.

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