Get recent events

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

Annotations declare readOnlyHint=false, so the agent knows this mutates state, and the description usefully discloses that it clears the buffer and returns events oldest-first. However, it does not say whether clearing is irreversible, whether consumed events are lost to other consumers, or what happens to buffered events beyond the limit — material for a consuming/clearing tool. There is also mild tension with destructiveHint=false given the word 'clear', which the description does not resolve.

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 front-loaded sentence with no filler; the ordering guarantee is placed last where it belongs. Nothing is redundant.

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?

With only two parameters and no output schema, the description is close to adequate for invocation, but it omits what an event object contains, whether truncation by limit leaves the remainder buffered, and what a subscription is. For a consuming/destructive-ish read these omissions matter more than for a pure getter.

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 coverage is 50%: limit is documented in the schema (max 100, default 25) while subscription_id has no description anywhere. The phrase 'oldest first' adds ordering meaning, but the description never explains what a subscription_id is or where to obtain one, which is the required parameter and therefore the biggest semantic gap.

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 a specific compound operation (read and clear) on a specific resource (buffered events for a subscription) plus an ordering guarantee (oldest first). An agent can distinguish it from list_events because of the 'clear' semantics, though the description never names that sibling to make the distinction explicit.

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 drain-and-consume usage pattern is implied by 'read and clear' but never stated as guidance. With list_events, subscribe_events, and unsubscribe_events in the sibling set, the description gives no explicit rule for when to call this instead of list_events (which presumably does not consume).

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