get_transcription_subtitles

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but the description does not state what the returned subtitles look like (format, encoding, structure), whether a file is produced, or any other behavioral characteristics. The only signal is the verb.

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 five-word phrase with no wasted words, front-loading the action and resource. It is concise, though it borders on being too terse to be genuinely informative.

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?

There is no output schema and no annotations, so the description is the only source of context. It fails to explain what format the subtitles take, how they relate to the transcription, or how to choose between this tool and the many sibling tools that also produce subtitle content. This leaves an agent uncertain about the return value and tool 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%; both asset_id and version_id are documented as UUIDs. The description adds no parameter-specific meaning beyond the schema, so the baseline of 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?

The description states a specific action ('Get') on a resource ('transcription') and the output form ('subtitles'), which is clear and not a tautology. However, it does not distinguish this from nearby sibling tools such as get_subtitle_webvtt, export_segments_srt, and export_segments_vtt, which also involve subtitle outputs, so the differentiation is incomplete.

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?

No guidance is provided on when to use this tool versus alternatives. The sibling list includes several tools that could plausibly return subtitle data (get_subtitle_webvtt, export_segments_srt, export_segments_vtt, list_asset_subtitles), but the description gives no selection criteria, exclusions, or context.

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