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

Beyond the readOnlyHint annotation, the description reveals important non-blocking behavior ('Results appear as they are fetched'), the exact per-entry return shape ('exactly what get_transcript returns ... plus its status'), and cost ('Free'). It does not contradict any 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 compact with four front-loaded sentences, each carrying distinct useful information: purpose/ordering, partial-result behavior, entry format, and cost. There is no filler, making it easy for an agent to parse quickly.

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 paginated read tool with a rich output schema and readOnlyHint, the description covers order, partial results, content shape, cost, pagination, and the timing. Nothing essential for 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?

Since the input schema already provides 100% description coverage for all three parameters, the description does not need to add parameter details. It only mentions next_page_token in a pagination example, adding no meaning beyond the schema.

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 uses a specific verb ('Read') and a clear resource ('finished transcripts from a batch job') plus ordering ('in the order submitted'), making the primary purpose unambiguous. However, it does not explicitly differentiate itself from the similarly named sibling get_transcripts_result, which could confuse an agent choosing between the two.

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 usage context: it can be called before the job completes and pagination is done with next_page_token. It does not mention any alternatives or when not to use the tool, so it falls short of explicit 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.