delete_webhook

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

With no annotations, the description carries the burden of behavioral disclosure. While it states that a success message is returned, it does not mention permissions required, irreversibility of deletion, side effects on dependent resources, or error behavior. For a destructive operation, this is insufficient.

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 concise and front-loaded with the main action, followed by a brief return-value note. Both sentences are purposeful with no redundancy or filler.

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 delete operation with an output schema, the description provides the essential purpose and return behavior. It does not elaborate on prerequisites or side effects, but the low complexity keeps the description reasonably complete. However, without annotations, a bit more detail on destructive effects would be beneficial.

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 100%, and the parameter description 'The ID of the webhook to delete' is self-explanatory. The tool description adds no additional semantic value beyond the schema, so the 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 action (delete), the resource (webhook), and the required identifier (ID). It distinguishes from siblings like create_webhook by using the opposite verb. The return behavior is also briefly mentioned, reinforcing the purpose.

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?

Usage is implied by the tool's name and description: it is used to delete a webhook. However, there is no explicit guidance on when to choose this tool over alternatives, such as when to avoid deleting or whether other operations (like updating) should be considered. The presence of create_webhook as a sibling suggests inverse usage but is not explicitly stated.

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