List webhook deliveries

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

Annotations only cover read-only/open-world, while the description adds real operational context: newest-first ordering, a 7-retry policy over ~9 hours, and a 7-day retention window for delivered and failed records. That retention detail directly tells an agent how far back a query can reach, which is not derivable from any structured field.

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?

Three tight sentences: what it returns, why to use it, then lifecycle constraints. Front-loaded with the resource and ordering, with zero filler.

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?

There is no output schema, so the description's enumeration of returned fields plus the retry/retention semantics covers exactly what an agent needs to interpret results and bound its expectations. Nothing material is missing for a 3-parameter read tool.

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 limit, status enum, and webhook_id are already documented in the schema. The description adds only the implicit scoping to 'one webhook endpoint' and the newest-first ordering, which is the expected baseline when the schema does the heavy lifting.

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 names a specific resource and scope: 'Recent deliveries to one webhook endpoint, newest first,' and enumerates the returned fields (event, payload, status, attempts, last error). It is clearly distinguishable from list_webhooks, though it never names a sibling explicitly.

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?

'Use it to check that events reach your receiver, or why they fail' gives concrete diagnostic scenarios for selecting this tool. There is no explicit when-not or named alternative, but the two use cases are unambiguous.

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