List Aircall contacts

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds the 'shared' scope constraint, which is not present in annotations or schema and clarifies that this is not a list of all contacts or personal contacts. This is valuable behavioral context beyond the structured data.

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, efficient sentence that conveys the essential purpose without redundancy. It is perfectly sized for a simple list 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, rich annotations, and comprehensively described schema (83% coverage), the description is nearly complete. It includes the key scope restriction ('shared') and does not need to explain return values since no output schema exists. Minor gap: it doesn't clarify what 'shared' means in the Aircall context, but this is not critical.

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 description coverage is 83%, so the parameters are mostly self-documenting. The description does not add any parameter-specific semantics; it solely says 'List shared Aircall contacts.' With high schema coverage, a 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 'List shared Aircall contacts' uses a specific verb ('list') with a clear resource ('shared Aircall contacts'), distinguishing it from siblings like aircall_get_contact (single contact) and aircall_search_contacts (search). The scope ('shared') adds precision.

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 phrase 'List shared Aircall contacts' implies usage for retrieving a batch of shared contacts, but there is no explicit guidance on when to prefer this over alternatives like search_contacts or get_contact. No exclusions or conditions are mentioned, so it is clear but underexplained.

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