Remove Webhook

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

No annotations are present, so the description fully handles behavioral disclosure. It clearly states the operation is irreversible, which is the key behavioral trait. It does not mention other potential side effects or permissions, but for a simple deletion this is adequate.

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 three sentences long, each adding essential information: purpose, safety instruction, and condition. It is front-loaded with the action. Slightly verbose but not excessive, earning a 4.

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 tool's low complexity (one parameter, no output schema, no annotations), the description covers the necessary aspects: action, prerequisite steps, and usage condition. It is complete enough for the agent to use the tool 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?

The only parameter is webhookId with schema coverage at 100% (description 'Webhook ID'). The tool description does not add further meaning to the parameter beyond what the schema provides, so baseline 3 applies.

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 specifies the verb 'Remove' and the resource 'webhook by ID' from 'Resend'. It clearly distinguishes the tool from sibling tools like create-webhook, get-webhook, update-webhook by focusing on deletion.

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 provides explicit when-to-use guidance: double-check with user, reference the endpoint, warn about irreversibility, and only use after explicit confirmation. It sets a clear condition and exclusion.

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