discord_delete_webhook

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

Describes token invalidation and permanent nature, adding meaningful behavioral context beyond annotations (destructiveHint: true). Clearly communicates consequences for integrations.

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 concise sentences: action, consequence, and permission. Information is front-loaded with no redundant text.

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?

Complete for a simple deletion tool: describes the action, irreversibility, and required permission. No output schema needed; all relevant context is provided.

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% for the single parameter webhook_id, with a basic description. The description adds no further meaning beyond what the schema provides, meeting the baseline.

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?

Clearly states 'Permanently delete a webhook by its ID' with a specific verb (delete) and resource (webhook). Distinguishes from sibling tools like discord_delete_webhook_message and discord_edit_webhook.

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?

Specifies required permission ('Manage Webhooks') and notes irreversibility. Does not explicitly state when not to use or list alternatives, but provides sufficient context for appropriate usage.

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