Delete Webhook

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

The description mentions a 'confirmation of deletion' return value, adding some behavioral context. However, annotations already indicate destructive and idempotent hints; the description does not elaborate on side effects or authorization beyond schema defaults.

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?

Extremely concise: two short paragraphs with clear structure. The purpose is stated first, followed by parameters and return value. No unnecessary words.

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 delete operation with only one parameter and no output schema, the description fully covers what the tool does and what it returns. It is complete given the tool's simplicity.

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 provides full coverage of webhook_id with pattern and description. The description merely restates 'Discord webhook ID' without adding new semantic information, so baseline score 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 clearly states the action ('Delete a webhook') using a specific verb and resource. It distinguishes itself from sibling tools like 'create', 'edit', and 'list' 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?

No explicit guidance on when to use this tool versus alternatives like editing or creating a webhook. While the delete context is straightforward, the description lacks criteria or prerequisites.

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