List Webhook Event Attempts

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

The read-only annotation already covers safety, and the description adds that attempts are returned most recent first with id, http_status_code, response body, and sent_at. This adds useful behavioral detail beyond what annotations provide, though it does not discuss pagination limits or failure behavior.

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?

The description is organized into labeled sections—Purpose, Returns, When to use—and each sentence carries distinct value. It is concise, front-loaded, and avoids filler.

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 purpose, return shape, and usage context even though there is no output schema. It provides the main prerequisite for eventId, but the source of webhookId is left implicit and pagination details rely entirely on the schema; these are minor gaps.

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 parameters are already well documented. The description adds useful context that eventId comes from list-webhook-events, but it does not meaningfully explain webhookId or the pagination parameters beyond what the schema already states.

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 and resource: 'List the delivery attempts Resend made for one webhook event,' and clarifies the ordering and return content. This clearly distinguishes it from sibling tools like list-webhook-events, which list events rather than attempts for a single event.

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?

There is an explicit 'When to use' section stating this is for events in failed or attempting status when the user wants to know why, and that it shows the endpoint's own error response. It also instructs the agent to get the event ID from list-webhook-events first, providing a clear precondition.

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