Delete webhook

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

Beyond annotations (destructiveHint: true), description details the exact destructive impact and the safety mechanism. It adds transparency by explaining the preview token behavior and that nothing changes on first call.

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?

Two sentences: first states purpose and effect, second explains usage pattern. Front-loaded, no filler, every sentence adds value.

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 no output schema, description explains return values (preview and confirm_token) and the two-phase flow. For a destructive tool with multiple steps, this is fully complete.

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 40% (webhook and guild documented). Description adds context for dry_run and confirm_token via the two-step explanation, but does not describe 'reason' parameter. This partially compensates for the low coverage but is not fully explicit.

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 clearly states 'Delete a webhook' and explains the effect: 'Anything still posting through it stops working.' This distinguishes it from other delete tools as specific to webhooks.

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?

Explicitly explains the two-step safe process: 'first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token deletes it.' This guides proper usage, though it doesn't mention alternative tools like update_webhook.

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