delete_webhook_subscription

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

With no annotations, the description does not disclose behavioral traits beyond the obvious mutation. There is no mention of whether the operation is destructive, what happens to associated data, or if confirmation is required. A delete operation should specify that it is irreversible.

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?

Extremely concise with one sentence that is front-loaded and contains no unnecessary words. Every word contributes meaning.

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?

Despite having an output schema and a simple parameter, the description lacks essential context such as return value, error conditions, and prerequisites (e.g., the subscription must exist). For a delete tool, this is insufficient.

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, subscription_id, is required but lacks any description in the schema (coverage 0%). The tool description does not explain what it is or how to obtain it, though the parameter name is somewhat self-explanatory. More context is needed for an AI agent.

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?

The description clearly states the action (delete) and resource (webhook subscription). It effectively distinguishes from sibling tools like create_webhook_subscription, update_webhook_subscription, and list_webhook_subscriptions.

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 provided on when or when not to use this tool. No mention of prerequisites, permissions, or consequences such as irreversibility. The tool name implies deletion, but the description offers no additional context for correct invocation.

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