dubbing_target_transcript_get

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that – no mention of what the transcript contains, whether it may be empty while generation is pending, or whether it requires the project/language to already exist.

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?

It is a single short phrase with no filler, so nothing needs trimming. However, its brevity reflects under-specification rather than discipline – there is no front-loaded scope, return info, or routing detail.

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 annotation coverage and no output schema, the structured data carries most of the load, but the description still fails to distinguish this tool from its many transcript siblings or to note any precondition (e.g. transcript must exist or be generated). It is too thin to route an agent reliably in a 200+ tool namespace.

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%, with both project_id and language_id documented in the schema itself, so the description is not required to compensate. It adds no meaning beyond the schema, which is the baseline-3 case for fully documented parameters.

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 'Get Dubbing Target Transcript' only restates the tool name/title in slightly reworded form. It identifies a resource and a retrieval verb, but provides zero differentiation from the many sibling retrieval tools in the dubbing/transcript family (dubbing_transcript_get, get_dubbing_transcripts, get_dubbed_transcript_file). An agent cannot tell which transcript variant to pick from the description alone.

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?

There is no guidance on when to use this tool versus siblings such as dubbing_transcript_get or dubbing_target_transcript_regenerate. Retrieval intent is implied by 'Get', but no prerequisites, context, or alternatives are stated.

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