Get recent events

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

Adds important behavioral detail: the tool clears buffered events after reading. This is a side effect not fully captured by annotations (readOnlyHint=false hints at mutation, but 'clear' specifies the exact mutation). Also discloses 'oldest first' ordering. No contradiction with 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?

A single sentence, front-loaded with the main verb, no unnecessary words. It delivers the key information efficiently.

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 simple tool with two parameters and no output schema, the description covers the primary behavior (read, clear, ordering). It could mention return format or pagination, but those are less critical given the simplicity.

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 describes 'limit' (max 100, default 25) but not 'subscription_id'. The description adds slight context ('from a subscription') but does not fully compensate for the missing parameter description. Since coverage is only 50%, the description could do more to clarify parameters.

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?

States 'Read and clear buffered events from a subscription, oldest first.' This provides a specific verb ('read and clear'), the target resource ('buffered events from a subscription'), and ordering ('oldest first'). It clearly distinguishes from siblings like list_events or get_event by emphasizing the subscription buffer and the clearing behavior.

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 context: when you need to consume events from a subscription and clear the buffer. It is clear about the scenario but does not explicitly contrast with alternatives like list_events or mention when not to use this tool.

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