delete_webhook

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

With no annotations, the description must carry the full burden. 'Permanently' usefully discloses irreversibility, which is the most important trait for a destructive call, but it says nothing about side effects (e.g. stopping active deliveries or losing webhook logs), required permissions, or failure modes.

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?

One short sentence, front-loaded with the key fact (permanence). Nothing is wasted, though it is arguably under-specified rather than genuinely concise.

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 an irreversible delete with no annotations, no output schema, and no documented parameters, the description does too little: it omits consequences, permission requirements, and what happens to dependent resources.

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 single parameter webhookId has 0% schema description coverage, so the description is the only place semantics could be added, and it adds nothing. Still, the parameter's meaning is self-evident from the tool name, so this is a modest rather than severe gap.

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?

States a specific verb and resource: 'Permanently delete a webhook subscription.' It is immediately distinguishable from siblings like update_webhook, create_webhook and test_webhook, though it never explicitly names an alternative.

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 on when to use this versus update_webhook (to disable) or test_webhook, no prerequisites, and no conditions under which deletion is appropriate. The word 'Permanently' is the only usage-adjacent signal.

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