spraay_webhook_delete

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

The description adds meaningful context beyond annotations: it states the action is permanent ('Removes it permanently') and mentions a cost ('$0.001 USDC'). It aligns with the destructiveHint annotation. It doesn't contradict any annotations. The idempotentHint is not addressed, but that's a minor gap.

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 highly concise: two sentences that immediately convey action, resource, effect, and cost. No redundant words. Front-loaded with the critical verb 'Delete'.

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?

While the description is clear, it omits details such as expected behavior when the webhook ID does not exist, error handling, or response structure. Given there is an output schema, this is partly compensated, but the description could be more complete for a destructive operation.

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 covers the only parameter (webhookId) with 100% coverage and includes a description. The tool description does not add additional semantic information beyond the schema. Baseline 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 action ('Delete', 'Removes it permanently') and the resource ('webhook by ID'). It distinguishes itself from sibling webhook tools (register, list, test) by focusing on deletion. The verb is specific and the resource is well-defined.

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 implies the tool is for permanent removal of a webhook, which is sufficient. However, it lacks explicit guidance on when not to use it (e.g., for temporary disabling) or mentions of alternatives. The context is clear but not elaborated.

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