dubbing_transcript_get

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered structurally. The description adds nothing beyond that — no indication of what transcript is selected (source vs target language), whether it can be empty, or remote-fetch behavior implied by openWorldHint.

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 four-word sentence with zero waste, but it is not appropriately sized for the information it must carry — it is under-specified rather than concise, conveying no more than the tool name already does.

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?

With no output schema and no explanation of what the returned transcript contains or how it relates to the sibling target/source transcript tools, the definition leaves key questions unanswered for a dubbing-domain retrieval tool. An agent would have to guess which of the several transcript endpoints to call.

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% for the single project_id parameter, which the schema documents as the identifier of the dubbing project. With full schema coverage and only one parameter, the baseline of 3 applies; the description adds no format or sourcing detail.

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?

"Get Dubbing Transcript" merely restates the tool name (title is even identical) with no added specificity. It does not distinguish this tool from close siblings such as get_dubbing_transcripts, get_dubbed_transcript_file, dubbing_target_transcript_get, or get_transcript_by_id, so an agent cannot tell which transcript resource this returns.

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 statement of when to use this tool versus alternatives, no preconditions, and no mention of the dubbing project state required. In a tool family with at least four near-identical transcript getters, the absence of routing guidance is a real gap.

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