list_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 discloses the core behavior: ranking conversations by byte count and targeting the largest flows. However, it does not state whether the operation is read-only, whether there are side effects, or what the ranking order/return format is, though 'largest flows' implies descending order.

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 with no filler. It conveys the action, resource, criterion, and use case efficiently, earning its place without unnecessary elaboration.

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 tool with three parameters, no annotation coverage, and zero schema descriptions, this description is too thin. It fails to define the required path, the meaning of top_n, or the expected protocol value format, and the presence of an output schema does not compensate for missing input semantics.

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. It partially covers the 'protocol' parameter by naming TCP, UDP, and IP, and it hints at the ranking metric. But it does not explain the required 'path' parameter or the 'top_n' behavior, leaving critical input semantics undocumented.

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 states the specific action ('Rank'), resource ('conversations'), scope ('TCP, UDP, or IP'), and criterion ('by bytes'), with a clear use case ('identifying the largest flows'). It does not explicitly distinguish itself from sibling tools, but the function is clear and unique enough among the listed siblings.

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 phrase 'when identifying the largest flows' gives an explicit context for when this tool is appropriate, and the protocol qualifier narrows the applicability. It does not mention alternatives or exclusions, but the stated use case is sufficient for an agent to select it.

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