webhook_delete_rule

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

No annotations are supplied, so the description carries the full behavioral burden. It labels the operation 'Write operation,' which is the only trait disclosed; it says nothing about permanence/irreversibility, required permissions, whether deleting a rule affects in-flight webhook deliveries, or failure behavior. For a destructive delete with zero annotation coverage this is a notable gap.

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, front-loaded sentences with no filler; the core action leads. 'Write operation' and the rule_id pointer overlap slightly with the schema and annotation-adjacent semantics, so it is not perfectly waste-free.

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?

A single-parameter delete with an output schema and no annotations. The description covers purpose, mutation class, and how to source the ID, and the output schema handles return values, but it omits the risk information an agent needs before invoking an irreversible delete. Adequate but thin for a destructive operation.

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%: the rule_id parameter is already documented as 'Rule ID — from webhook_list_rules.' The description adds no syntax, format, or range detail beyond restating that same provenance, so the 3 baseline applies.

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?

Names a specific verb and resource ('Delete a webhook routing rule'), which is immediately distinguishable from the sibling verbs webhook_create_rule, webhook_update_rule, and webhook_list_rules. It stops short of explicitly contrasting itself with those siblings, but the verb+resource pairing is 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 explicitly routes the agent to webhook_list_rules as the way to obtain the required rule_id, which is real selection guidance for the prerequisite step. It gives no guidance on when not to delete or on alternative tools for removal scenarios, so it falls short of the top band.

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