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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the REST route, disclosing nothing about irreversibility, whether associated shares/configuration are also removed, or failure behavior for an unknown id.

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?

Two short fragments with zero filler and the purpose front-loaded before the route. It is terse rather than bloated, though the second fragment is largely redundant with the tool name.

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, no-output-schema operation this is thin: it omits irreversibility, any cascade effects on shared webhook bots, and error semantics for missing ids. The presence of destructive annotations covers part of the burden, but the description leaves real gaps.

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% and the single 'id' property is an untyped string with no description. The path template '/webhook/bot/{id}' is the only hint that this identifies a bot webhook, but the description never states the format, source, or validity conditions of that id.

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 names a specific verb and resource ('Delete bot webhook'), which is clear and unambiguous. It does not, however, distinguish this tool from the closely named sibling delete_webhook_bot_share_id, which targets a different sub-resource, so sibling differentiation is left to the tool name alone.

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?

There is no statement of when this tool should be used versus alternatives, no prerequisites (e.g. ownership or auth scope), and no exclusions. An agent must infer all routing logic from the tool name and the crowded delete_* sibling list.

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