youtube.transcript.get

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Retrieve transcript using approved modes' but lacks information about side effects, permission requirements, error behavior, or output format. The modes are listed in the schema but not explained.

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 very short (one sentence), which is concise, but it lacks necessary substance. It front-loads the action but does not provide enough information to be useful. Under-specification is not a virtue.

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 4 parameters, no output schema, and no annotations, the description fails to provide a complete picture. It does not explain how to use the tool, what the transcript output looks like, or how the different modes work. The context is severely lacking.

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 0%, yet the description does not explain any parameters. It only mentions 'approved modes' without elaborating on the 'mode' enum values or other parameters like 'video', 'language', or 'transcriptText'. The meaning of these parameters is entirely missing.

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 'Retrieve transcript', which clearly indicates the verb and resource. However, it does not distinguish from sibling tool 'youtube.transcript.analyze', which likely analyzes a transcript. The mention of 'approved modes' adds some specificity but is vague.

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 description mentions 'provided_text supported; OAuth captions planned' but does not explain how to choose a mode or when to prefer this tool over sibling tools.

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