delete_webhook

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

Annotations already provide destructiveHint and idempotentHint. The description adds a user confirmation note beyond annotations, which is valuable. However, it does not explain consequences like irreversibility or cascading effects, missing an opportunity for fuller transparency.

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 overly repetitive: 'Delete a webhook' appears three times, and 'Deletes a record' is redundant. The opening tag line is useful, but the rest could be condensed into one or two sentences, wasting space.

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 tool with one parameter and no output schema, the description covers the basic action. However, it lacks details on error handling (e.g., webhook not found) and success response, making it only 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?

The input schema fully describes the 'id' parameter with coverage 100%. The description adds no additional meaning about the parameter, such as where to find the ID or validation rules, so the baseline score of 3 applies.

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 a webhook' and the resource type. The name and symbol reinforce the purpose. However, the description is repetitive with three nearly identical statements, which slightly reduces clarity.

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 includes a safety instruction 'Confirm with the user before calling,' which helps guide proper use. However, it does not explicitly differentiate from other delete tools like 'delete_a_record' or 'update_webhook,' leaving the choice to the agent's implicit understanding.

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