get_conversations

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

No annotations are provided, so the description carries the full burden. It describes the tool's output and defaults but lacks details on performance, memory usage, or error handling (e.g., file not found). This is adequate but not deep.

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 only four sentences plus structured Args/Returns. The first sentence immediately states the purpose. Every sentence adds value without 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?

Given the tool's moderate complexity and the presence of an output schema, the description adequately covers purpose, parameters, and return values. It could mention file-not-found behavior or performance considerations, but it is largely complete for this tool.

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 coverage is 0%, but the description adds meaningful explanations for all three parameters: 'file_path' is path to pcap/pcapng, 'max_packets' is maximum to analyze (default 100000), and 'top_n' returns top N conversations (default 20). This compensates well for the missing schema descriptions.

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?

Description clearly states 'Extract network conversations/flows from a pcap file', which is a specific verb+resource. It further explains the purpose ('see which hosts are communicating') and distinguishes from siblings like 'pcap_summary' and 'get_connections' by focusing on top bandwidth consumers.

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 clear use cases: 'Useful for identifying top bandwidth consumers.' It implies when to use but does not explicitly state when not to use or mention alternative tools for detailed analysis.

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