capture_conversations

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool performs live capture (as opposed to reading from a file) and focuses on TCP/UDP conversations. However, it does not disclose potential side effects (e.g., resource usage, need for root privileges, or impact on the network interface), which is a notable gap for a live capture tool.

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, front-loaded with the core purpose, and uses bullet-like 'Use this when' for guidelines. Every sentence adds value, and it is appropriately sized for the tool's simplicity.

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?

The description gives the tool's purpose and usage context, but with no output schema and no annotations, it doesn't fully explain what the returned 'conversation statistics' will look like or any prerequisites/assumptions. For a tool with only 3 optional parameters, this is adequate but leaves gaps in the agent's understanding of the result format.

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 input schema has 100% description coverage, with each parameter (duration, interface, tshark_path) already documented. The description does not add any parameter-specific meaning beyond this. According to the rubric, the baseline for high schema coverage is 3, and the description provides no additional value for parameter semantics.

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's function: 'Capture live traffic and provide TCP/UDP conversation statistics.' It uses a specific verb (Capture) and resource (live traffic), and specifies the output (conversation statistics). This distinguishes it from sibling tools like capture_packets (raw capture) and get_top_talkers (top talkers), though it doesn't explicitly name them.

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 provides explicit use cases: 'Use this when: 1) User wants conversation details, 2) Identifying communicating pairs, 3) Network mapping.' This gives clear context for when to invoke the tool. However, it doesn't mention when not to use it or explicitly name alternative tools, so it falls short of a 5.

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