rm_delete_webhook

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is established. The description adds a valuable behavioral requirement: 'requires confirm=True'. This goes beyond the schema, which only shows confirm as optional with default false, and is critical for correctly invoking the tool.

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 one short sentence that front-loads the action and includes the most important safety constraint. Every word earns its place; there is no filler, redundancy, or unnecessary detail.

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 two-parameter destructive operation with an output schema and safety annotations, the description covers the essential non-obvious behavior: confirmation is required. The webhook_id requirement is visible in the schema, so the description does not need to restate it. It is slightly minimal but sufficient for an agent to select and invoke the tool correctly.

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 0%, so the description carries the burden of explaining parameters. It only adds meaning to 'confirm' by stating it is required for deletion. It says nothing about 'webhook_id', leaving the agent to infer its role from the schema alone. This is only partial compensation for the missing schema descriptions.

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 verb and resource: 'Delete a webhook subscription.' This clearly distinguishes the tool from sibling tools like rm_create_webhook and rm_list_webhooks. The parenthetical about confirmation adds useful operational context without obscuring the core purpose.

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 makes the general use case clear: this is the tool for deleting a webhook. However, it does not explicitly describe when to use it versus alternatives, nor does it mention prerequisites like finding the webhook_id first via rm_list_webhooks or creating webhooks with rm_create_webhook.

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