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

Annotations already mark destructiveHint=true and idempotentHint=true, but the description adds critical behavioral context: 'Permanently delete' and 'This cannot be undone' reinforce irreversibility, and the note that endpoint/global events are unaffected clarifies side effects. This goes beyond the annotations without contradicting them.

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 two concise sentences with no filler. The core action is front-loaded, and the irreversibility warning is placed immediately after. Every word adds value, and the structure is scannable for an agent.

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 that the tool has an output schema, full parameter documentation, and annotations covering destructiveness and idempotency, the description is complete for an agent to call it correctly. The irreversibility and scope notes fill the key gap that structured fields do not capture. It could mention return format or confirmation behavior, but the output schema likely covers that, so nothing essential is missing.

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 all three parameters (id, environment, workspaceId) are fully documented in the input schema. The description adds no additional parameter-level detail or usage nuance, so it meets the baseline for high schema coverage but does not exceed it.

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 opens with a precise verb and resource: 'Permanently delete a webhook subscription.' It immediately specifies the scope ('webhooks group') and clarifies what is NOT affected (endpoint and global events), which differentiates it from sibling tools like delete_webhook_endpoint. This makes the tool's purpose unambiguous.

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 does not explicitly name an alternative or give a 'when to use' directive, but it does explain that the endpoint and its global events are unaffected, implying that this tool is specifically for subscriptions rather than endpoints. This gives contextual guidance that helps an agent pick the right tool, though it stops short of an explicit 'use this instead of X when...' statement.

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