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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful pagination mechanics (next_cursor, complete flag) and return structure (segments with speaker, timing, link), which go beyond the 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?

Three sentences, front-loaded with usage context followed by behavioral details. No redundant or filler phrasing; each sentence contributes useful information.

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 straightforward read-only retrieval tool, the description covers purpose, when to use it, return shape, and pagination. Output schema exists so return values need not be explained, but the remaining gap is thin parameter guidance for meeting_id and cursor input.

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 low (33%, only page_size documented). The description implies cursor semantics through 'next_cursor returns the next page', but does not explain meeting_id or page_size. It partially compensates for the gap but leaves two parameters under-specified.

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 action ('reads a transcript') and resource, with concrete content details (who said what, speaker labels, timestamps, exact words). It is clearly distinct from siblings like list_recordings or export_meeting, though it does not name an alternative explicitly.

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 usage context: 'Use this when the user wants the transcript of a meeting...'. No exclusions or named alternatives are provided, but the trigger condition is unambiguous.

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