delete_webhook

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

Since no annotations are provided, the description carries full burden. It correctly signals destructive behavior ('Delete') and access restriction ('admin only'), but lacks details such as irreversibility, side effects, or error conditions. A score of 3 reflects adequate but incomplete disclosure.

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 conveys all essential information. It wastes no words, though it could be slightly more structured without losing 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 low-complexity tool with one parameter and no output schema, the description covers the most important aspects: action, resource, identifier, and access. It is nearly complete, though it could mention that the webhook must exist or what the response is.

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 input schema already describes the parameter ('Webhook ID to delete') with 100% coverage. The description adds no extra meaning beyond 'by ID', so it meets the baseline of 3 without adding further value.

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 scope ('by ID'), which immediately distinguishes it from siblings like delete_agent. The addition of '(admin only)' further clarifies its intended user role.

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 a key context cue by noting 'admin only', indicating when the tool is appropriate. However, it does not explicitly state when not to use it or mention alternatives (e.g., a bulk delete operation is not available among siblings).

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