List webhook deliveries

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

Annotations only declare readOnlyHint=true, so the description adds substantial behavioral value: delivery ordering, status enum semantics, failure-field explanations, pagination, admin auth requirement, and the organization-level 404 signal. This goes well beyond what annotations already convey.

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 dense sentences cover purpose, ordering, statuses, failure explanation, pagination, auth, and a common error signal without redundancy. Every sentence earns its place and the core purpose is front-loaded.

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 successfully explains key response semantics: status values, lastResponseStatusCode, lastError, and pagination. It does not describe the exact response envelope, but the agent has enough behavioral and error context to invoke the tool and interpret results correctly.

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 id, limit, and cursor. The description does not add new parameter-level meaning beyond the schema; it only reinforces pagination context already captured in the cursor and limit descriptions.

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 uses a specific verb ('List') and identifies a precise resource ('one subscription's delivery attempts'), and 'most recent first' adds scope. This clearly distinguishes it from sibling tools like list_webhooks (subscriptions) and deliver_webhook (manual dispatch).

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 description gives clear context: this targets one subscription, is paginated, requires an Admin token, and has a specific 404 failure meaning. It does not explicitly name alternatives or state when-not-to-use, so it falls short of a 5, but the constraints are clear enough for correct selection.

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