List Webhook Deliveries

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description goes further with retention (~30 days), result ordering, the exact status lifecycle values, and the explicit note that payloads are omitted and where to get them. With no output schema, this added context is genuinely load-bearing.

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?

Front-loaded with the action and ordering, then fields, retention, and the sibling redirect. Every sentence supplies distinct information with no padding.

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 no output schema, the description compensates by enumerating the returned row fields, status enum, retention window, and ordering, and it points to the right tool for payload data. Nothing needed to call it correctly is missing.

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 description coverage is 100% and all four params (limit, start, status, endpointId) are documented in the schema itself. The description only alludes to filtering ('filtered to one') and repeats the status values, adding little beyond the schema — baseline 3 is appropriate.

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+resource ('List recent webhook delivery attempts') plus ordering (newest first) and scope (all endpoints or filtered to one). It is clearly distinguishable from get_webhook_delivery, list_webhooks, and resend_webhook, which sit in the same sibling group.

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?

Explicitly says when to reach for it ('audit what was sent', 'find a delivery id to resend') and routes the agent elsewhere for the payload ('use get_webhook_delivery for the full signed payload'). That is a concrete when-to-use plus a named alternative.

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