Get recent events

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

The description states 'clear buffered events', which is a destructive action, but annotations set destructiveHint=false, creating a direct contradiction. According to rubric, score 1 if description contradicts annotations.

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 sentence with no wasted words, directly stating the core behavior and ordering.

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 simple tool (2 params, no output schema), the description covers the basic behavior but lacks details on return format, edge cases, or effect of 'clear'. The contradiction with annotations also reduces completeness.

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 50% (one param described). The description adds no extra meaning beyond the schema; it only restates that events are from a subscription. Baseline 3 is appropriate.

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 the verb ('Read and clear'), resource ('buffered events from a subscription'), and ordering ('oldest first'). It distinguishes from sibling tools like 'list_events' (which lists all events) and 'subscribe_events' (which creates the subscription).

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 implies usage for polling buffered events from a subscription but does not explicitly state when to use this tool vs alternatives (e.g., 'list_events' for non-buffered events) or provide when-not-to-use guidance.

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