aircall_add_campaign_numbers

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds context that the operation targets a power dialer campaign and is user-specific, but does not disclose behaviors such as duplicate handling, idempotency, or whether it replaces existing numbers. No contradiction with 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 concise sentence that front-loads the verb and resource, with no extraneous information. It is appropriately sized for a simple operation.

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?

Given the tool's simplicity, two fully documented parameters, and no output schema, the description plus annotations are largely sufficient. It could mention edge cases like duplicate numbers or behavior when the campaign does not exist, but these are not essential for basic invocation.

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 schema fully describes both parameters (user_id and phone_numbers in E.164 format) with 100% coverage. The description does not add additional semantic meaning beyond what the schema already provides, 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 uses the specific verb 'Add' with the resource 'phone numbers to a user's power dialer campaign,' clearly stating the action and target. It distinguishes itself from sibling tools like aircall_remove_campaign_number and aircall_get_campaign_numbers by focusing on adding numbers.

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 when to use the tool (when adding phone numbers to a user's power dialer campaign) but provides no explicit guidance on alternatives, prerequisites, or when not to use it. It lacks comparison to sibling tools like aircall_remove_campaign_number or aircall_get_campaign_numbers.

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