youtube_transcripts

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

No annotations are provided, so the description carries full burden. It discloses the credit cost, shares the /youtube endpoint with other tools, and explains that the presence of `v` selects this behavior. It also describes the return format. It does not mention destructive actions, which is appropriate for a read-only tool.

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 fairly concise and front-loaded with the main purpose. It includes necessary operational notes (credits, endpoint sharing, verified live date, return format) without being overly verbose. Minor improvements could remove redundant info like the date.

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?

Given no output schema, the description describes the return format. It also addresses the endpoint nuance and credit cost. It does not cover error conditions or prerequisites, but for a simple transcript extraction, it is fairly complete and distinguishable from sibling tools.

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 100%, so baseline is 3. The description adds value by explaining that `v` selects the Transcripts behavior on the shared endpoint and provides an example of how to find the video ID. This enhances understanding beyond the schema descriptions.

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 the tool extracts the complete transcript from a YouTube video as an array of text segments with start time and duration. The verb 'extracts' and resource 'transcript' are specific, and it distinguishes itself from sibling tools like youtube_search, youtube_comments, and youtube_video.

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 mentions it is the cheapest YouTube endpoint at 1 credit and explains how the `v` parameter selects this behavior on the shared /youtube endpoint. It also notes the endpoint discrepancy (docs show bare /youtube but working endpoint is /youtube/transcripts). However, it does not explicitly say when not to use it, though the context with sibling tools makes it clear.

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