list_webhook_deliveries

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

With no annotations, the description carries the full behavioral disclosure burden. It clearly indicates a read-only listing operation and the statuses returned, but it does not mention pagination, ordering, time range, or whether delivery payloads are included. 'Recent' is vague.

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 conveys the action, resource, relevant statuses, and purpose. There is no wasted wording or redundant schema repetition.

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 low-complexity read-only list tool with one optional parameter and no output schema, the description is largely complete. It states what is listed and why, though it could add a note about what 'recent' means or how limit interacts with results.

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 0%, and the description does not mention the 'limit' parameter at all. While 'limit' is a fairly self-explanatory name, the description provides no added meaning about how it affects results or whether it applies to statuses or time range.

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 verb ('List') and resource ('webhook delivery attempts'), and clarifies the statuses included. This clearly distinguishes it from sibling tools like list_webhooks, which list configured webhooks rather than delivery attempts.

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 phrase 'for debugging' gives some context for when to use the tool, but it does not explicitly mention alternatives or when not to use it. There is no guidance distinguishing it from list_webhooks or list_webhook_event_types.

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