conversations

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

With no annotations, the description carries the full burden of disclosing behavior, but it only says "statistics" and lists type options. It does not state whether the operation is read-only, what capture must refer to, how the results are shaped, or what constraints apply to the capture parameter.

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 short and contains no filler, and the type constraint is immediately useful. However, it is telegraphic and lacks a clear verb or structured explanation of the tool's behavior.

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 tool has no output schema and no annotations, yet the description leaves out core details such as what capture identifies, what the result contains, and how type changes the result. An agent would struggle to call this tool correctly beyond knowing capture is required.

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, but it only documents the allowed values for type. The required capture parameter is completely unexplained, and the description does not clarify how type affects the returned conversation statistics.

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?

"Conversation statistics" names a resource and the type field gives some specificity, but there is no verb explaining what the tool does with conversations. It also does not distinguish itself from sibling tools like endpoints, protocol_hierarchy, or io_stats, which could plausibly return similar or overlapping statistics.

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 no guidance on when to use this tool versus alternatives such as endpoints, protocol_hierarchy, or io_stats. It only states that type is one of tcp, udp, ip, eth, which is not enough for an agent to choose this tool confidently.

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