List recent events

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

Beyond the readOnlyHint annotation, the description discloses ordering (newest first), the default 7-day window, the data source (events export), and a concrete permission requirement (an owner's or admin's key). It also enumerates the attributed fields returned, which is real behavioral context rather than restatement.

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 dense paragraph that front-loads the resource, contents, and default window before the usage hint. The opening 'Read-only' duplicates the annotation, a minor redundancy in an otherwise efficient definition.

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?

No output schema exists, and the description compensates by enumerating the returned fields and their attribution chain. Combined with the auth note and default window, an agent has everything needed to call it correctly.

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 100%, so from/to/slug/limit are already documented, including the default window and the 20-item limit. The description restates the default window but adds no syntax or filtering nuances beyond the schema, so baseline 3 applies.

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 verb and resource (list recent conversion and revenue events) plus the precise contents returned, ordering, and default window. It is clearly distinguishable from siblings like list_taps, record_event, and get_analytics.

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?

Gives an explicit use case ('check that purchases or sign-ups arrive'), which tells the agent when to reach for it. It stops short of naming alternatives (e.g., list_taps for raw tap data or get_analytics for aggregates) or stating 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.