discord_delete_webhook_message

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

Annotations already mark this as destructive (destructiveHint: true), and the description reinforces this with 'Permanently delete' and 'IRREVERSIBLE.' It also adds a meaningful prerequisite beyond the schema: the original webhook token must be used. No contradiction with annotations exists.

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 brief and front-loads the core destructive action. There is slight redundancy between 'Permanently delete' and 'IRREVERSIBLE,' and the token requirement is repeated from the schema, but the overall structure is efficient and easy to parse.

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 the destructive annotations and complete parameter schema, the description provides enough context to invoke the tool correctly: the target resource, necessary credentials, and irreversibility. It does not describe response behavior or error cases, but no output schema exists and this is a simple delete operation, so the omission is not critical.

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 description coverage is 100%, so all three parameters are already well documented. The description adds minimal semantic value beyond the schema, mainly clarifying that the token must be the original webhook token. This meets the baseline for fully-covered schema parameters without adding substantial meaning.

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 states a specific action — permanently deleting a message sent through a webhook — and identifies the required auth context (webhook ID and token). The phrase 'through a webhook' clearly distinguishes it from sibling tools like discord_delete_message, which handles non-webhook messages.

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 clearly implies this tool is for webhook-sent messages and emphasizes that the original webhook token is required. It does not explicitly name alternatives or say when not to use it, but the webhook-specific framing is strong enough to guide selection among the many sibling message tools.

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