Delete webhook

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

The description adds behavioral context beyond the destructiveHint annotation by stating 'This cannot be undone,' emphasizing irreversibility. This is useful for an agent deciding whether to invoke the tool, though the annotation already indicates destructive potential.

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 a single concise sentence with no filler. The key information (delete operation, permanence, target by ID) is front-loaded.

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 deletion tool with one documented parameter and a destructiveHint annotation, the description provides sufficient context. The irreversibility warning and ID requirement cover the essential operational details, though no output schema exists to clarify return values.

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 input schema fully documents the single 'id' parameter as a webhook ID (UUID). The description's reference to 'by its ID' aligns with the schema but does not add additional semantic detail beyond what the schema already provides.

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 tool's function: 'Permanently delete a webhook by its ID.' The verb 'delete' and resource 'webhook' are specific, and the description distinguishes it from sibling webhook operations (get, create, update, validate, list).

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 implies the tool is for removing webhooks, but it does not explicitly state when to use it versus alternatives like update_webhook or other means of disabling. No exclusions or alternative references are provided, so usage guidance is minimal.

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