aircall_delete_voicemail

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

The annotations already declare destructiveHint=true, but the description adds meaningful context by stating 'Permanently delete' and 'This cannot be undone.' This discloses irreversibility and specifically identifies what gets destroyed (the voicemail of a call), going beyond the generic destructive flag.

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?

Two short sentences, front-loaded with the main action ('Permanently delete') and an immediate consequence. Every word earns its place; no filler or repetition.

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 single-parameter destructive tool, the description covers purpose, permanence, and the affected resource. It lacks any mention of error conditions or preconditions (e.g., voicemail existence), but given the simplicity and strong annotations, it is nearly 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 the parameter call_id described as 'The call ID.' The description does not add extra parameter detail, but none is needed since the schema fully documents it. 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 tool's function: 'Permanently delete the voicemail of a call.' The verb 'delete' and resource 'voicemail' are specific, and it distinguishes from similar tools like aircall_delete_recording and aircall_archive_call. The emphasis on 'permanently' and 'cannot be undone' reinforces the action's scope.

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?

No explicit usage guidance is provided. The description does not mention when to use this tool versus alternatives (e.g., when to delete a voicemail vs. a recording), nor does it state any preconditions or exclusions. The context of usage is entirely implied by the tool's name and purpose.

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