List sent events

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

Annotations already declare readOnlyHint and closed-world scope, so the safety profile is covered. The description usefully adds ordering (newest first) and the contents of the returned payloads (change list plus flight snapshot at the time), but 'recent' is undefined and there is no mention of retention, pagination, or what happens past the limit.

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?

Two sentences, front-loaded with what is listed and how it is ordered, followed by the practical use cases. Nothing is wasted and nothing important is buried.

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 two-parameter, read-only listing tool with an annotation-declared safety profile and full schema coverage, the description covers returned content and ordering well. The main missing pieces are the relationship to list_deliveries and any indication of the retention window, which matter for choosing between the two 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?

Schema coverage is 100%, and the schema documents both the subscription id format and the 1-100 limit with its default. The description adds no parameter meaning beyond that, so the baseline of 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?

The description uses a specific verb and resource ('Recent events generated for a subscription') and adds concrete scope: newest first, with the exact webhook payloads that were sent. It does not name or contrast with the closely related sibling list_deliveries, so the distinction between 'events' and 'deliveries' is left implicit.

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?

It gives two explicit use cases ('see what changed and when' and 'replay a payload into a local receiver'), which is clear usage context. It offers no exclusions or alternative routing, notably against list_deliveries, which an agent could plausibly pick instead for the same investigation.

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