conversations

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

The description discloses caching behavior (first call scans PCAP, subsequent pages from cache) and pagination. However, it does not state whether the tool is read-only or if it has side effects. With no annotations, this is adequate but not comprehensive.

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 extremely concise, with two short paragraphs that front-load the purpose. Every sentence adds meaningful information 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 no output schema, the description should detail the return format beyond 'sums frames/bytes per peer pair'. It does not specify whether the output is a list of objects or details the columns. Acceptable but not fully 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 explains `sort_by`, `skip`, `limit`, and implies `alias` (layer). It also notes `limit=0` for all results. But it omits `display_filter` and `type` parameters, which are not covered by the schema descriptions (0% coverage). Thus it partially compensates but leaves gaps.

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 it's a conversation table for a given layer, summing frames/bytes per peer pair. It distinguishes itself from sibling tools like 'endpoints' or 'protocol_hierarchy' by focusing on peer pairs, but does not explicitly contrast 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?

No explicit guidance on when to use this tool versus alternatives. It describes sorting and paging but does not indicate when to choose 'conversations' over other tools.

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