youtube_transcript

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

No annotations are provided, so the description carries the full burden. It mentions language fallback and timestamped output, but lacks information on error handling, rate limits, authentication, or limitations on available transcripts.

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?

Three concise sentences; the purpose is front-loaded, followed by input and behavior. No superfluous words.

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 2 parameters and an output schema, the description is adequate but missing guidance on error scenarios and assumptions (e.g., subtitles must exist). It covers the core functionality but not edge cases.

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 0%, and the description only partially compensates: it mentions 'video URL or ID' for the required parameter and hints at 'lang' through language preferences, but does not explain the array type or null default.

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 clearly states 'Get subtitles/transcript for a YouTube video,' using a specific verb and resource. It distinguishes from sibling tools like youtube_channel_info and youtube_video_info by focusing solely on transcript retrieval.

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 description explains input format ('Accepts a video URL or ID') and default language behavior, but does not explicitly state when to use this tool versus alternatives or address prerequisites (e.g., video must have subtitles enabled).

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