delete_webhook

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

With no annotations to rely on, the description adds only the 'admin only' behavioral constraint. It does not disclose that deletion is typically irreversible, nor does it mention any side effects or rate limits. The description is minimally transparent beyond the access restriction.

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 with no redundancies. It front-loads the action and resource, achieving maximum conciseness.

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 delete operation with one parameter and no output schema, the description provides the essential purpose and access constraint. It could mention irreversibility or return value, but the current level is largely adequate given the tool's simplicity.

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%, so the input schema already documents the parameter with its description. The description adds no additional semantic value beyond what is in the schema. Baseline score 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) and resource (webhook), specifies the identifier (by ID), and includes an access constraint (admin only). It effectively distinguishes from sibling tools like create_webhook and list_webhooks.

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 indicates that the tool is admin-only, which provides some usage context, but it does not explicitly state when to use this tool versus alternatives (e.g., when to delete vs. list or create webhooks). No recommendations or exclusions are given.

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