webhooks_deliveries

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds only that results are paginated and filterable by status, event type, and date range, which are largely restatements of schema capabilities. It says nothing about ordering, retention, or rate limits, so it adds modest value beyond annotations.

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 short sentences with no filler: purpose first, filter capabilities second, sibling routing third. It is front-loaded and every sentence 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 paginated list tool with full schema coverage and annotations carrying the safety profile, the definition covers what an agent needs to invoke it and to know when to switch to the detail sibling. No output schema exists, so some return-shape detail is absent, but for a list operation this is a minor gap.

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 each parameter (uuid, from/to, page, limit, status, eventType, companyId) is already documented. The description repeats the filter categories and the success/failed statuses without adding format, default, or precedence details 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 (Retrieve) and resource (paginated list of delivery attempts for a webhook endpoint), and explicitly distinguishes itself from webhooks_delivery_detail by naming that sibling for payload inspection. An agent can select it correctly without opening any schema.

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?

Provides clear routing: use this tool for lists of delivery attempts, and use webhooks_delivery_detail when full request/response payloads are needed. It does not mention other nearby siblings like webhooks_events (event-type catalogue) or webhooks_list, so a small gap remains, but the primary alternative is handled explicitly.

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