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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the transcript is verbatim, limited to 100 lines/4000 characters per page, and requires resuming with both offsets, including within a long line. This goes beyond the schema and 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?

Two sentences, front-loaded with the core purpose and key constraints. Every clause earns its place: verbatim, single recording, page limits, and the exact resume mechanism. No filler.

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?

Given the output schema exists and annotations cover safety, the description is nearly complete. It explains pagination and the tricky text_offset behavior. It could mention what happens at the end of the transcript or how to detect completion, but the output schema likely covers that. The main gap is not explicitly stating when to use this versus get_transcripts_by_participant, but the 'ONE recording' qualifier handles 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 67%: conversation_id and text_offset are described in the schema, but offset is not. The description adds meaning by explaining the pagination contract (use both next_offset and next_text_offset) and the 'within a long line' nuance, which clarifies how text_offset behaves. It doesn't fully explain offset's default or relationship, but the pagination guidance compensates.

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 states a specific verb ('get') and resource ('verbatim transcript of ONE recording'), and distinguishes itself from siblings by emphasizing 'verbatim' and 'ONE recording' versus summaries or participant-based retrieval. The '[content_fetch]' tag and pagination details further clarify its 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 clearly implies when to use it: when a verbatim transcript of a single recording is needed, and it provides explicit pagination instructions ('Resume using both next_offset and next_text_offset'). It does not explicitly name alternatives or exclusions, but the sibling list and 'verbatim' qualifier make the context clear.

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