Read a call's transcript

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

The readOnlyHint annotation already establishes this is a safe read operation, so the description is not obligated to restate safety. It adds only that the payload is turn-by-turn conversation content, which is mildly useful but silent on pagination, speaker labeling, or whether the transcript can be absent for short/failed calls.

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?

One compact sentence with zero filler and the key scope constraint front-loaded. It is efficient, though it verges on under-specification rather than being deliberately tight.

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?

With no output schema and an undocumented required parameter, the description needed to carry more weight. It says nothing about identifier format, transcript availability, or how it differs from get_call, so an agent has real gaps to close before invoking it.

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 0%, so the single callUuid parameter is documented nowhere. The description does not explain that the identifier must be a call UUID or where to obtain it (e.g., from list_calls or get_call), leaving the caller to guess the format.

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 names a specific resource and scope: the turn-by-turn transcript of a single call. An agent can tell it returns conversation turns rather than call metadata. It does not, however, distinguish itself from the sibling get_call, which an agent might reasonably confuse it with.

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?

There is no statement of when to use this tool versus get_call, get_lead_for_call, or any alternative. No prerequisites, no conditions, no exclusions. The agent must infer everything from the name alone.

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