delete_webhook_rule

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

No annotations exist, but description fully discloses destructive, irreversible nature and the required gating flags. This is exemplary transparency about behavior.

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?

Description is extremely concise with action, warning, endpoint, and conditions. Uses bullet and emoji for emphasis. No superfluous content.

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?

Adequately warns about destructiveness but omits parameter explanation and return values. For a simple destructive action, it covers the main risks, but parameter details are 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 coverage is 0%, so description must explain parameters. It only mentions confirm requirement implicitly but does not describe rule_id or the confirm parameter's role. Lacks semantic detail for both parameters.

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?

Description states 'Delete a webhook rule' with HTTP endpoint, clearly identifying the verb and resource. Differentiates from sibling tools like create_webhook_rule and update_webhook_rule.

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?

Description warns about irreversible production changes and specifies double-gating requirements (DROPSCAN_ALLOW_WRITES=1 and confirm=true). Provides clear context but does not explicitly mention when to avoid using this tool.

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