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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, covering the safety profile. However, the description adds no additional behavioral context beyond the basic action—such as permanence of deletion, impact on associated resources, or irreversibility. With annotations doing the heavy lifting, the description contributes no extra transparency value.

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 that accurately states the purpose without any fluff or redundancy. It earns its place by being the minimal necessary statement, though it could be slightly more informative without harming conciseness.

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?

Given the tool's simplicity—one required parameter, full schema coverage, annotations covering destructive and idempotent behavior, and an output schema present—the description is adequate. However, it misses an opportunity to mention common relevant context, such as that the deletion is permanent or that the webhook stops receiving events immediately. The structured fields carry most of the informational burden, so the thin description is acceptable but not complete.

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%: the 'id' parameter is described as 'The webhook endpoint id, as returned by list_webhooks or create_webhook.' The tool description itself adds no parameter-level meaning. Baseline of 3 is appropriate because the schema fully documents the parameter, and the description does not need to compensate.

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 'Deletes a webhook endpoint' clearly states the verb 'delete' and the resource 'webhook endpoint'. It unambiguously distinguishes itself from sibling tools like create_webhook, update_webhook, get_webhook, and list_webhooks. No ambiguity exists about what action this tool performs.

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 provides no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. While the name and description imply it is used when a webhook needs to be removed, the description itself offers no conditional context or routing to related tools. This is a minimal, single-purpose description without usage direction.

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