aircall_delete_phone

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

The annotations already declare destructiveHint=true, so the destructive nature is known. The description does not add extra context beyond what annotations provide, such as irreversibility, permissions required, or cascading effects. It is consistent with annotations and adds minimal behavioral detail, so a neutral score is warranted.

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, compact sentence: 'Delete a phone number from a contact.' It is front-loaded with the main verb and contains no unnecessary words or fluff. Every word earns its place.

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 two-parameter delete operation with a destructiveHint annotation and full schema coverage, the description is adequately complete. It clearly states the purpose and the relationship between the parameters. It does not explain what happens if the phone number is not found or if it is the last number, but that is not essential for typical usage.

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 provides clear descriptions for both parameters ('The phone number ID to delete' and 'The contact ID'), covering 100% of schema properties. The tool description adds relational context ('from a contact') which slightly reinforces the link between parameters, but it does not significantly clarify anything beyond the schema.

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 target ('a phone number'), and the context ('from a contact'), making it easy to distinguish from sibling tools like aircall_delete_contact or aircall_delete_email. It is specific and unambiguous.

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 no guidance on when to use this tool versus alternatives. It does not mention, for example, that deleting a contact's last phone number might have side effects, or that aircall_delete_contact should be used to remove an entire contact. This is a basic operation with no usage context.

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