aircall_delete_webhook

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

The description adds the behavioral consequence that the URL will no longer receive event notifications, which goes beyond the destructiveHint annotation. However, it does not disclose other aspects such as permanence or any required permissions. Given the annotation already marks destructive, this is adequate but not rich.

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 extremely concise: two short sentences, with the main action in the first word and the consequence in the second sentence. No filler or redundant information, earning a perfect score.

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?

The tool is simple (one parameter), the annotations provide destructive hint, and the description clarifies the purpose and effect. This is sufficient for an AI agent to understand the tool's behavior. While it doesn't reference sibling webhook tools or mention irreversible deletion, the low complexity and existing annotations make this 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 100% with a single parameter, webhook_id, whose description ('The webhook ID to delete') already provides full clarity. The tool description adds no additional parameter semantics, so the baseline 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.' It identifies the specific resource (webhook) and the action (delete), and adds a specific consequence ('The URL will no longer receive event notifications'), which distinguishes it from sibling tools like create/update/get/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 implies usage context: it is for deleting a webhook, and the consequence is stated. However, it does not explicitly provide guidance on when to use this tool versus alternatives (e.g., 'Use when you want to stop notifications; use update to modify instead'). The context is clear but not explicit about exclusions.

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