list_call_transcripts

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses that transcripts are fetched in parallel server-side, that calls without transcripts are included but marked 'No transcript available', and that the tool retrieves complete customer + operator dialogue. Pagination behavior is also explained.

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 well-structured with a summary, use cases, behavior notes, pagination guidance, and an Args list. However, there is some redundancy: the parallel transcript fetching and full-transcript inclusion are mentioned in both the main text and the Args section, making it slightly longer than necessary.

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?

Despite having 6 parameters and no annotations, the description is remarkably complete: it covers the core purpose, filtering options, pagination strategy, default/max values, and the behavior with missing transcripts. The presence of an output schema further reduces the need to describe return values, so no crucial context 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?

The input schema has zero descriptions (0% coverage), so the detailed Args section fully compensates. It explains date format (YYYY-MM-DD), that user accepts display or login names and is 'Resolved automatically', that queue expects an internal name usable with list_queues, and that take has default 20 and max 50.

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 'List answered calls with their full speech-to-text transcripts inline', making the purpose specific and distinct from siblings like list_calls or get_call_transcript. It also positions itself as 'the primary tool for analyzing call quality', reinforcing its unique role.

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 provides clear use cases: 'analyzing call quality, identifying calls requiring management attention, detecting escalations, or reviewing agent performance', and gives pagination guidance. However, it does not explicitly name alternatives or state when not to use this tool, so it lacks the explicit when/when-not contrast required for a 5.

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