get_transcript

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds the useful precondition that only completed transcripts are fetchable, but the format/response-shape details are duplicated from the schema and there is no mention of what happens if the transcript is not yet ready.

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?

A single front-loaded sentence with no filler; the resource, identifier, and possible output shapes all appear immediately.

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 two-parameter read tool with full schema coverage, an output-shape hint, and complete annotations, the description is nearly sufficient. The main omission is behavior on a non-completed or unknown transcript ID, which an agent would want to know before calling.

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 coverage is 100% and the format enum already documents that segments is the default and text/srt/vtt return export bodies. The description merely restates those format options without adding semantics beyond the schema, so baseline 3 applies.

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?

Names a specific verb (Fetch) and resource (completed transcript) plus the ID key, so the agent knows exactly what it retrieves. It does not distinguish itself from the sibling get_video_transcript, leaving ambiguity about which transcript tool to pick.

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 word 'completed' implies this only works after a job has succeeded, and listing formats hints at the export use case. There are no explicit when-to-use/when-not rules and no reference to alternatives like get_video_transcript or wait_for_job for pending jobs.

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