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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: newest-first ordering, the meaning of 'direction' and 'from' on inbound calls, and that a call_ref from results feeds wa_ai_call_get and pagination.

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?

Two sentences, fully front-loaded with scope and ordering first, then the follow-up directive. Every clause (direction, from, answers_inbound, call_ref) carries information an agent needs and none is redundant.

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?

An output schema exists, so return values needn't be explained, and the description supplies the filtering/ordering semantics and the transcript follow-up path. Minor gaps on rate limits or result volume handling keep it from a 5, but nothing essential to correct invocation is missing.

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 100%, so the schema already documents 'limit' (1-100, default 25) and 'before' (prior-page call_ref). The description reinforces pagination via call_ref but adds no new syntax or constraints beyond what the schema provides, so the baseline 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?

States a specific verb and resource ('List this workspace's AI voice-agent calls, newest first') and precisely scopes what qualifies as a call: outbound calls started with wa_ai_call_start and inbound calls answered by a preset whose answers_inbound is true. This clearly distinguishes it from the sibling wa_list_calls.

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?

Gives clear context for use and explicitly routes the agent to wa_ai_call_get with a call_ref for transcripts and recordings. It does not explicitly state when not to use this tool (e.g., vs. wa_list_calls for non-AI calls), so it falls just short of full when/when-not guidance.

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