Delete webhook

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

Annotations already flag destructiveHint=true, but the description adds substantial beyond-annotation context: deliveries stop immediately, the signing secret is destroyed, a re-registered URL gets a new secret, old receivers fail verification, and non-owned endpoints return 404 to avoid leaking existence.

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?

Three sentences carry dense, relevant information with no filler. The primary action is front-loaded, followed by immediate consequences and a privacy-relevant edge case.

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 single-parameter destructive tool with no output schema, the description covers the action, immediate effects, security implications, and failure semantics. Nothing needed for invoking or understanding the call 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 coverage is 100%, and the schema already states the webhookId is the 'Webhook endpoint UUID to delete.' The description reinforces ownership and the URL concept but adds little new parameter-specific meaning beyond what the schema 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 uses a specific verb and resource: 'Permanently delete one of your webhook endpoints.' It clearly distinguishes deletion from the neighboring create_webhook and list_webhooks operations even without naming them.

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 intended use is implied clearly: call this when you want to permanently remove a webhook endpoint you own. However, it does not explicitly mention alternatives or conditions like 'use create_webhook to re-register,' so the when-vs-alternative guidance is only implied.

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