List Webhooks

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

With readOnlyHint: true already annotating the safe read nature, the description adds useful behavioral context by specifying the output content (webhook IDs, endpoints, events). It does not contradict the annotation and provides meaningful detail about what the tool returns, which is especially helpful given no output schema.

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 two sentences, front-loaded with the main action, and every phrase adds value. It is concise with no redundancy, making it easy for an agent to parse quickly.

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 the simple nature of the tool (no params, read-only annotation), the description fully covers the context: what it lists, what info it returns, and what it does not cover. The absence of an output schema is compensated by stating the key output fields (IDs, endpoints, events).

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?

The tool has zero parameters, so there is no parameter information needed. The baseline for 0 params is 4, and the description appropriately focuses on the tool's purpose rather than parameter details.

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 action and resource: 'List all webhooks from Resend.' It clearly distinguishes from sibling tools by explicitly saying 'Not for listing emails, segments, or broadcasts,' making the purpose unmistakable.

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 tells the user when to use this tool: 'Use to get webhook IDs and see which endpoints and events are configured.' It also provides exclusions ('Not for listing emails, segments, or broadcasts') which differentiates from alternative list tools among siblings.

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