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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description's added availability timing and transcript content are useful extras. There is no contradiction with annotations, and the description appropriately clarifies that this tool is not usable during an active call.

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, no filler, with the core purpose front-loaded. The availability condition is a valuable addition and is placed second without bloating the description.

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 one-parameter, read-only tool with an output schema and strong annotations, the description covers everything needed: what the tool returns and when it can be called. Nothing critical 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 fully describes the only parameter ('id' as the call ID) with 100% coverage. The description adds no parameter-specific detail, but none is really needed for a single, clearly documented field.

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 a specific verb ('Get') and resource ('full transcript of a phone call'), with details on content (speaker labels, timestamps, confidence scores). This sets it apart from sibling tools like phone_call_get and phone_call_recording_get, which serve different retrieval needs.

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?

It gives a clear temporal constraint: 'Available after the call ends and transcription completes.' This tells an agent when it is appropriate to call this tool. It does not explicitly name alternatives, but the scope is clear enough to route the agent away from recording or call metadata tools.

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