discord_delete_webhook

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

With no annotations, the description carries the full burden of behavioral disclosure. It communicates the destructive act of deletion and the confirm flag requirement, but it does not explicitly state irreversibility, permission requirements, or why confirmation may be needed. The 'confirmation enabled' condition is also ambiguous.

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 two concise sentences, front-loaded with the core action and immediately followed with the condition for confirmation. There is no unnecessary wording or filler.

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?

The tool is a simple delete operation, and the output schema helps clarify return expectations. Still, without annotations and with most parameters unexplored, the description is only minimally adequate. It mentions the confirm condition but omits context about guild_id usage and the meaning of reason.

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?

The schema has 0% description coverage, and the description only explains the confirm parameter. The webhook_id, guild_id, and reason parameters are left entirely to their titles, so the description does not compensate for the lack of schema documentation.

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' with a specific verb and resource. It distinguishes this from sibling webhook tools like create, edit, get, and list because the action is unambiguous.

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 includes a conditional usage requirement: 'Requires confirm=true when confirmation is enabled.' However, it does not explicitly state when to choose this tool over sibling tools or mention any stop conditions or alternatives, though the operation is largely self-evident from the name.

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