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

The description says 'Delete', implying irreversible destructive behavior, but annotations declare destructiveHint=false. This is a direct contradiction. The description does not add any other behavioral context (e.g., irreversibility, permission requirements, side effects) that would compensate for the missing annotation.

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 extremely short but repeats the same information twice ('Delete Workspace Webhook' and 'Delete the specified workspace webhook'). The bulk support note is useful but the duplication wastes space. It could be condensed to a single clear sentence.

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?

This is a delete operation with no output schema, no parameter explanations, and no behavioral warnings. It lacks critical context such as whether deletion is permanent, if any confirmation or cascade effects occur, or what the response contains. For a destructive operation, this is inadequate.

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 description only mentions 'webhook_ids' for batch support but fails to explain the required 'webhook_id' parameter or the 'account' parameter. With 0% schema description coverage, the description does nothing to clarify parameter semantics beyond what the schema property names already imply. It adds no meaning about formats, defaults, or relationships.

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 action (delete) and resource (workspace webhook). It also mentions bulk support, which adds a distinguishing feature. However, the first two sentences are nearly identical ('Delete Workspace Webhook' vs 'Delete the specified workspace webhook'), which is slightly redundant but not confusing.

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?

No guidance is provided on when to use this tool versus alternative deletion tools (e.g., other elevenlabs_delete_* tools) or any prerequisites like required permissions or context. The only hint is the resource name, which implies usage for workspace webhooks, but there is no explicit when/when-not guidance.

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