beaconed_webhooks_delete

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

Annotations already include destructiveHint: true and idempotentHint: true, but the description adds crucial behavioral detail: 'permanently remove' and 'deliveries stop immediately.' This goes beyond the annotation by specifying permanence and immediate effect, which is valuable for an agent deciding whether to invoke it.

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, efficient sentence that leads with the HTTP method and endpoint, then states the action and consequence. No wasted words, perfectly front-loaded.

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 one-parameter tool with no output schema and annotations already covering safety, the description is complete. It tells the agent exactly what the tool does, the destructive effect, and the immediate consequence. Nothing essential is missing.

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 schema already documents the single parameter (id as Webhook UUID) with 100% coverage. The description adds no extra parameter semantics, but the schema is sufficient, so a baseline of 3 is appropriate.

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 HTTP method (DELETE), the resource (webhooks/{id}), and the action (permanently remove a webhook subscription). It distinguishes itself from sibling webhook tools (list, get, create, update, test) by the explicit removal semantics.

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 usage context is clear from the description: use this when you need to permanently remove a webhook. It does not explicitly contrast with alternatives (e.g., using update to disable), but the destructive nature and immediate effect make the use case self-evident. A small gap is not explicitly saying 'use update if you only need to pause deliveries'.

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