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

The readOnlyHint=true annotation already covers the safe read behavior. The description adds the REST endpoint but provides little additional behavioral context such as pagination behavior, rate limits, or return format beyond what the schema already declares.

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 concise with two short sentences, front-loaded with the core action. The second sentence about the REST endpoint is somewhat redundant but not verbose or counterproductive.

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 comprehensive input schema and the read-only annotation, the description is adequately complete for a list operation. It lacks explicit differentiation from aircall_search_calls and return format details, but these are not critical given the context.

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?

All six parameters have full descriptions in the schema (100% coverage). The description's mention of 'creation-date window' and 'ordered' merely echoes the schema's from/to and order fields, adding no extra semantic value.

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 'List calls' with a specific verb and resource, and mentions optional filtering by creation date and ordering. This distinguishes it from sibling tools like aircall_get_call (single call) and aircall_search_calls (search-based).

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 through 'optionally filtered by a creation-date window and ordered' but does not explicitly state when to use this tool versus aircall_search_calls or other alternatives. No exclusions or alternative guidance is provided.

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