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

With readOnlyHint=true in annotations, the safety profile is already declared. The description adds context that the action items are AI-extracted via the Aircall AI Voice feature, but does not disclose behavior like pagination or error handling. This is acceptable but not rich beyond the 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 one clear sentence followed by the REST endpoint, with no wasted words. It is front-loaded with the primary purpose and immediately specifies the API reference.

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 single-parameter GET tool, the description is complete: it states what is returned (action items/follow-ups). Since there is no output schema, the plural 'items' implies a list, but return structure is not detailed. This is adequate for the tool's simplicity.

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: it describes 'id' as 'The call id.' The description adds no further parameter meaning, but the schema fully documents the only parameter, so the baseline 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 clearly states the tool retrieves AI-extracted action items/follow-ups from a call, with a specific REST endpoint. This distinguishes it from sibling tools like aircall_get_call_summary or aircall_get_call_transcription by naming the exact resource.

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 gives clear context: use this when you need action items or follow-ups from a call. It does not explicitly mention alternatives or exclusions, but the purpose is specific enough that an agent can decide when to invoke it.

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