delete_webhook_subscription

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

No annotations exist, so the description must fully convey behavioral traits. It states 'delete' implying destruction but omits consequences like cascading deletes, permission requirements, reversibility, or error conditions (e.g., if subscription does not exist). This is insufficient for a destructive operation.

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?

The description is a single sentence with no superfluous words. It is direct and front-loaded with the essential information.

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?

The tool has an output schema (not shown) which reduces the need to describe return values. However, for a delete operation, the description should mention whether it is idempotent, what happens if the subscription ID is invalid, or any side effects. The current description is minimal but functionally adequate.

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 input schema has a single required parameter 'subscription_id' with 0% schema description coverage. The tool description does not elaborate on the parameter's format, source, or constraints, relying solely on the name which is generic. No added value beyond the schema.

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) along with the identifier method (by ID). It uniquely distinguishes this tool from siblings like get_webhook_subscription or test_webhook_subscription.

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 is provided on when to use this tool versus alternatives such as update_webhook_subscription or test_webhook_subscription. The description does not mention prerequisites, contexts, or scenarios where deletion is appropriate versus other operations.

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