live_events

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

No annotations are provided, and the description lacks behavioral details. The term 'drain' suggests a destructive or mutating operation, but this is not confirmed. Side effects, permissions, and response behavior are not disclosed.

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 very short but lacks essential information. It is not concise in a helpful way; it is under-specified, leaving ambiguity about the tool's operation.

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 lack of annotations, output schema, and parameter descriptions, the description is completely insufficient. It does not explain what the tool returns, its side effects, or how it fits into the broader context of sibling tools.

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 only parameter 'limit' has no description in the schema (0% coverage) and is not explained in the tool description. The description adds no meaning beyond the schema, failing to clarify its role (e.g., maximum number of events to drain).

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 'Drain retained Live listener events' uses a specific verb 'Drain' and identifies a resource, but does not clarify what 'drain' means in this context (e.g., remove, process) or what 'retained Live listener events' are. It distinguishes from siblings like 'live_call' or 'live_set' but is still vague.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it.

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