webhook_delete

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description adds value by stating 'Voog returns 204' (HTTP status on success) and the required 'force=true' flag, which are beyond what annotations provide.

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 concise sentences, front-loaded with the action and endpoint. Every sentence provides essential information without unnecessary verbosity.

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?

Given no output schema, the description includes the HTTP response code (204) and prerequisites. It does not cover error cases or side effects, but for a simple delete operation it is adequately complete.

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 coverage is 67% (2 of 3 parameters have descriptions). The description adds meaning by explaining the requirement for 'force=true' and advising to retrieve the id via webhooks_list. The 'site' parameter lacks a description in the schema, but the description does not address it, slightly reducing completeness.

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 specifies 'Remove a webhook (DELETE /webhooks/{id})', which includes the verb 'remove', the resource 'webhook', and the exact HTTP method and endpoint. It clearly differentiates from sibling tools like webhook_create and webhooks_list.

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 provides explicit usage conditions: 'Requires force=true; without it the call is rejected' and 'Run webhooks_list first to confirm the id.' While it does not explicitly state when not to use it, the prerequisite and mandatory parameter are clearly communicated.

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