List Webhook Deliveries

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds 'delivery attempts' context but does not elaborate on pagination or filter behavior. It adequately complements annotations without contradiction.

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?

Single sentence with no wasted words. Front-loaded with the action and resource. Efficient and to the point.

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?

The description covers the core purpose but lacks guidance on pagination (cursor, limit) and filtering (status, event_type). With an output schema present, return structure detail is less critical, but given the 5-parameter complexity, more context would improve usability.

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 60% with descriptions for id, limit, and cursor, but two parameters (status, event_type) have no description. The tool description adds no additional meaning to any parameter beyond the schema, missing an opportunity to explain filters or pagination usage.

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?

Description clearly states 'List delivery attempts for a webhook endpoint,' using a specific verb and resource. It distinguishes from sibling tools like 'get_webhook_delivery' (single delivery) and 'list_webhooks' (different resource).

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?

No guidance is provided on when to use this tool versus alternatives like get_webhook_delivery or replay_webhook_delivery. The description does not mention required prerequisites (e.g., needing a webhook ID) or filtering options.

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