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

Annotations already mark destructiveHint=true and readOnlyHint=false. The description adds 'Cannot be undone,' which specifies irreversibility beyond the annotation. This is useful behavioral context and does not contradict annotations.

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 very short sentences with zero redundancy: 'Permanently delete a webhook endpoint. Cannot be undone.' The action and key caveat are front-loaded with no extraneous wording.

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 simple deletion tool, the description covers the core action and irreversibility. However, it omits any mention of the id parameter or how to obtain it, and does not address success/failure behavior. Given the minimal schema and no output schema, a bit more detail would improve completeness.

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 coverage is 0% for the single 'id' parameter, and the description does not explain what the id refers to or how it relates to the endpoint. The tool name and title imply it's the endpoint id, but the description adds no parameter-specific guidance.

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 verb 'delete' and the resource 'webhook endpoint', and emphasizes permanence. It distinguishes from sibling tools like create, update, and list by the explicit deletion semantics and irreversibility.

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 implies usage (to permanently remove a webhook endpoint) but does not explicitly mention when to use it vs. alternatives like update (to deactivate) or rotateSecret. No direction is given on prerequisites or finding the id, though the action itself is straightforward.

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