Delete a webhook

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description's only added value is the rate limit (100 requests / 10 seconds per shop), which is genuine operational context, but it says nothing about permanence, effect on pending deliveries, or the 'confirm' requirement.

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?

Very short with no filler sentences, though the rate-limit banner is placed ahead of the purpose statement, which slightly buries the front-loaded intent. Nothing is wasted, but nothing is elaborated either.

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 destructive, non-idempotent, open-world deletion with no output schema, the description should warn that the action is irreversible and note whether dependent webhook events are affected. Neither the description nor the schema covers consequences, leaving a real gap for a destructive tool.

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 (account, confirm, webhook_configuration_id) are already documented in the schema. The description adds no parameter-level meaning, which is the expected baseline when the schema does the heavy lifting.

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+resource ('Delete a webhook') that cleanly distinguishes it from siblings create_webhook, update_webhook, get_webhook, and list_webhooks. It is clear but offers no scope detail (e.g. whether the webhook is removed permanently or only deactivated).

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 or disable-style siblings, and no prerequisites, confirmations, or warnings about irreversibility. The agent must infer everything from the name alone.

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