Get Webhook Event

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

Annotations only provide readOnlyHint, so the description carries the behavioral disclosure burden. It does this well by enumerating exact return fields and explaining that next_attempt_at is null once the event reaches a terminal state. It does not mention error cases or rate limits, but those are not critical for a simple read operation.

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 compact and uses bolded labels for Purpose, Returns, and When to use. Every sentence serves a distinct function and the key purpose is front-loaded. There is no redundant phrasing or unnecessary background.

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?

This is a low-complexity read-only tool with two required parameters and no output schema. The description covers purpose, return payload semantics, and when to use it, including how to source the event ID. Nothing essential is missing for an agent to invoke it 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 coverage is 100%, so the schema already documents both parameter names and types. The description adds meaningful provenance by stating the event ID should come from list-webhook-events first, which is operational knowledge beyond the schema. The webhookId parameter gets no extra explanation, but the baseline is already satisfied by the schema.

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 states a specific verb and resource: 'Get one event delivered to a webhook, including the exact payload Resend sent to the endpoint.' This clearly distinguishes it from listing events or retrieving webhook configuration, and the 'one event' phrasing reinforces the singular scope.

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 'When to use' section explicitly states the intended scenarios: seeing what Resend actually sent for a specific event, or checking when the next retry is due. It also tells the agent to obtain the event ID from list-webhook-events first, providing a concrete prerequisite and routing to the correct sibling tool.

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