get_meeting_transcript

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

There are no annotations, so the description carries the burden of behavioral disclosure. It indicates the output includes speaker labels and timestamps, which is useful. However, it does not explicitly state that the operation is read-only, nor does it describe error behavior (e.g., invalid meeting_id) or permission requirements. The 'get' verb implies read, but more explicit disclosure would be better.

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, concise sentence with no extraneous text. It front-loads the main action ('Get the full transcript') and specifies key output details, making it efficient and easy to parse.

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 tool with one parameter and no annotations, the description is fairly complete: it states what is returned (full transcript with speaker labels/timestamps) and the target resource. It does not explicitly contrast with overlapping sibling tools, but the schema provides context for finding IDs. Given the absence of an output schema, the description adequately communicates the return value, though it could mention failure cases or prerequisites.

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 schema already covers 100% of the parameter (meeting_id) with a helpful description pointing to list_meetings. The tool description does not add any additional parameter semantics, so the baseline score of 3 is appropriate.

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 the tool retrieves the full transcript for a specific meeting, with speaker labels and timestamps. This distinguishes it from siblings like search_transcripts (searching partial content) and get_speaker_contributions (per-speaker breakdown), making its purpose unambiguous.

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 fetching a complete transcript when a meeting_id is known, but it does not explicitly mention when to use it over alternatives. The schema hint ('use list_meetings to find IDs') provides some guidance, yet the description itself lacks direct comparison to siblings like search_transcripts.

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