delete_webhook_subscription

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

With no annotations, the description carries the full disclosure burden, and it offers a genuinely useful operational fact: the required OURA_CLIENT_ID and OURA_CLIENT_SECRET environment variables. However, for a destructive operation it omits whether deletion is permanent/irreversible, whether it is idempotent, and any error behavior, leaving notable gaps.

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 short, front-loaded sentences with zero filler — the core action leads and the prerequisite follows. Every sentence earns its place.

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 simple single-parameter delete tool this covers the essentials (action plus auth requirement), but with no annotations and no output schema, it leaves the irreversibility and post-delete behavior of a destructive call unstated.

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% and there is only one parameter ('id', already documented as 'The webhook subscription ID'), so the schema does the heavy lifting. The description adds no additional meaning about the id format or source, 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 ('Delete a webhook subscription'), which cleanly separates it from the list_/get_/create_/update_/renew_webhook_subscription siblings. An agent can identify exactly what this does without opening the schema.

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?

The description explains what the tool does but gives no guidance on when to delete versus updating or renewing a subscription, nor any exclusions or prerequisites beyond the auth note. Usage must be inferred entirely from the name.

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