List Webhook Events

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

The readOnlyHint annotation already signals no mutation, and the description adds meaningful behavior beyond that: results are ordered most recent first, and it discloses the return shape and the exact status values (pending, attempting, success, failed). No contradictions with 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?

The description is organized into Purpose, NOT for, Returns, and When to use sections. Each section earns its place and provides distinct, decision-relevant information without filler or repeated boilerplate.

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?

Given there is no output schema, the description properly documents the return fields and status enum. It also covers exact usage criteria, exclusions, and follow-up tools. Pagination behavior is already in the input schema, so nothing needed for correct invocation is missing.

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 baseline is 3. The description does little to enrich parameter meaning beyond the schema; it only reinforces that the webhookId refers to a single webhook. It does not add details about cursor format or pagination beyond what the schema already provides.

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 names a specific resource and action: list events that Resend delivered to one webhook. It clearly differentiates from siblings like get-webhook, list-emails, and the Events product, so an agent can identify this tool immediately.

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?

It explicitly says what this tool is NOT for, names the alternatives for those cases, and provides concrete user-intent triggers such as 'did my webhook receive this?'. It also tells the agent what to call next (get-webhook-event, list-webhook-event-attempts), giving clear routing guidance.

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