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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds value beyond them: the concrete consequence (notifications stop flowing), the permission prerequisite, and the exact retry protocol. It doesn't state whether the deletion is reversible or what the response contains, but against rich annotations this is strong.

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?

Three short sentences, front-loaded with the action and its effect, then prerequisites, then the failure-recovery rule. No filler, and each sentence carries distinct information.

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 destructive, idempotent mutation with no output schema, the definition covers permission requirements, user confirmation, and retry semantics. Missing only the return shape and reversibility, which are minor given the annotation coverage.

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 webhookId, workspaceId, and idempotencyKey are fully documented in the schema, making 3 the baseline. The description restates the idempotencyKey retry rule and hints at confirming webhookId but adds no new syntax or format meaning 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?

States a specific verb and resource ('Delete a Workspace webhook subscription') plus the effect ('stop future notifications through it'), which separates it from create/update/regenerate-secret siblings in the webhook cluster. It never names an alternative explicitly, so sibling differentiation is implied by the verb rather than stated.

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?

Adds real operational context: settings permission required, confirm the selected subscription, and retry the identical body/idempotencyKey on a lost response. It lacks an explicit routing statement such as 'to change a webhook's URL use company_update_webhook instead', which is the only gap.

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