Delete webhook

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

Annotations already declare destructiveHint=true, and the description goes beyond that by disclosing exactly what is destroyed: future deliveries stop and the delivery log is removed with it. It also names the return shape { ok, message }. It stops short of saying whether the deletion is reversible or what permission is required.

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 compact clauses: the action with its consequence front-loaded, then the return contract. No filler and nothing repeated from the structured fields.

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 one-parameter destructive tool with annotations and full schema coverage, this is nearly complete: mutation effect, collateral data loss, and return value are all covered. The remaining gap is whether the operation is permanent or has any restore path.

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?

Only one parameter, and the schema already documents it at 100% coverage ("Webhook id (from list_webhooks)"). The description adds nothing about the id's format or sourcing, so the baseline 3 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?

States a specific verb and resource ("Remove a webhook") and immediately qualifies scope with "(unsubscribe)." It is unmistakably distinct from create_webhook, update_webhook, and list_webhooks, though it never names a sibling to route the agent.

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?

There is no when-to-use / when-not-to-use guidance and no alternative named (e.g., update_webhook to disable delivery without deleting). The word "unsubscribe" only implies the use case rather than stating conditions or prerequisites.

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