aircall_delete_config

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

Annotations already provide destructiveHint=true, and the description aligns with that by saying 'Delete'. It adds the scope 'messaging configuration for an Aircall number' but no extra behavioral context like irreversibility or side effects. It does not contradict annotations.

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 sentence that says exactly what is needed with no filler. It is front-loaded with the action and resource, making it easy to parse.

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?

This is a simple delete tool with one parameter, no output schema, and helpful annotations. The description adequately covers the tool's function and target. It does not explain the response or post-conditions, but for a simple delete with annotations, this is sufficient.

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 has 100% coverage with a clear description for number_id ('The Aircall number ID'). The tool description's phrase 'for an Aircall number' mirrors the schema but adds no additional meaning or format details. Baseline 3 is appropriate given full schema coverage.

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 a specific action ('Delete') targeting a specific resource ('messaging configuration') scoped to an Aircall number. It distinguishes from sibling tools like aircall_delete_campaign or aircall_create_config, making the tool's purpose 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 implies usage (when you need to delete a messaging config) but lacks explicit guidance on when to prefer this over alternatives or any exclusions. No alternative tools are mentioned, and no when-not-to-use conditions are stated.

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