webhooks_deliveries

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

No annotations are provided, so the description carries some burden. It discloses that results are paginated and filterable, which is useful. However, it does not describe return format, ordering, error behavior, or rate limits. For a read-only listing tool the gap is moderate.

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, zero filler. First sentence states the core purpose and capability, second sentence provides the sibling-tool pointer. Every element earns its place.

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 read-only list tool with 100% schema coverage and a clear pointer to the detail tool, the description is largely complete. It could mention default ordering or that delivery attempts return summary data only, but these are minor gaps given the schema richness.

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%, so the schema fully documents all 8 parameters. The description adds minimal parameter-level value but mentions the status/event/date filtering options at a high level. Baseline 3 applies given complete schema coverage.

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?

Clear verb+resource: 'Retrieve a paginated list of delivery attempts for a webhook endpoint.' The description distinguishes purpose well and explicitly references sibling tool webhooks_delivery_detail for deeper inspection, setting it apart from related webhook tools.

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?

States when to use (list delivery attempts) and explicitly points to webhooks_delivery_detail for payload inspection - an explicit alternative. Filtering capabilities (status/event type/date range) are enumerated, giving clear context on use cases.

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