get_transcript

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

No annotations are provided, so the description carries the burden of explaining behavior. It discloses the output type and its characteristics ('full', 'speaker-labelled', 'timestamped'), which helps an agent understand what will be returned. It does not mention side effects, authorization requirements, or potential unavailability of transcripts, but 'get' reasonably implies a read-only operation.

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 a single front-loaded sentence that directly states the resource and its key attributes. There is no redundant wording or filler, and every word contributes meaning.

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 simple one-parameter retrieval tool, the description is mostly complete: it identifies the input, the output, and distinguishing transcript features. It falls slightly short by not providing any explicit usage guidance or disambiguation from sibling tools, though the purpose is clear enough for straightforward selection.

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 100%, and the meeting_id parameter is already documented with a source hint ('get from list_meetings'). The tool description itself adds no parameter detail, but it does not need to because the schema fully covers the single parameter.

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 and resource ('Get the full speaker-labelled, timestamped transcript') and clearly identifies what is returned. This distinguishes it from sibling tools like get_summary and get_action_items without needing to inspect them.

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 implies the tool is for retrieving a transcript when the user needs the full speaker-labelled, timestamped record of a meeting. However, it does not explicitly state when to prefer this over get_summary or search_meetings, nor does it offer any exclusions or alternative routing.

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