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

The description goes beyond the destructiveHint annotation by explaining the action is destructive, requires authorization, and mentions that webhook test dispatch is not exposed. This gives the agent a clear understanding of side effects and limitations.

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 sentences, concise, and directly addresses purpose, usage prerequisite, and side effects without any redundant content.

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 tool with one parameter and no output schema, the description covers the primary purpose, a necessary prerequisite for the parameter, and the destructive nature of the operation. It is sufficiently complete for an agent to invoke it 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?

The single parameter subscription_id is described in the schema as 'Webhook subscription ID.' The description adds that it should be obtained from list-webhook-subscriptions, which provides helpful sourcing context beyond the schema.

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 purpose: removing a webhook subscription or stopping event delivery. It uses a specific verb 'remove' and provides a clear user intent scenario, making it easy to distinguish from creation or updating webhook tools.

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?

It explicitly states when to use the tool and notes that subscription_id should come from list-webhook-subscriptions, providing a practical prerequisite. It does not explicitly compare against alternatives like update-webhook-subscription, but the guidance is sufficient for correct usage.

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