Remove Webhook

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

With no annotations present, the description fully carries the burden of disclosing behavioral traits. It explicitly states the operation is irreversible, requires user confirmation, and should reference the endpoint. This goes beyond the basic delete semantics and provides critical safety context for an agent.

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 and front-loaded with the purpose. However, the confirmation requirement is repeated twice ('double-check' and 'explicitly confirms'), adding slight redundancy. It remains compact and mostly every sentence earns its place.

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?

For a simple deletion tool with one parameter and no output schema, the description is sufficiently complete. It explains the action, the safety protocol, the irreversibility, and the condition for invocation. The agent has all necessary context 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 input schema already covers the only parameter (webhookId) with a type and description, giving 100% schema coverage. The description's 'by ID' adds no additional meaning beyond the schema, so a baseline of 3 is appropriate since the schema does the heavy lifting.

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 begins with 'Remove a webhook by ID from Resend', which clearly identifies the action (remove), the resource (webhook), and the scope (by ID). This distinguishes it from sibling webhook tools like create-webhook, list-webhooks, get-webhook, and update-webhook, which perform different operations.

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 preconditions for use: 'you MUST double-check with the user', 'You may only use this tool if the user explicitly confirms'. It also gives guidance on what to reference (ENDPOINT) and what to warn about (irreversible), making when-to-use and when-not-to-use exceptionally clear.

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