get_youtube_transcript

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

Without annotations, the description notes the fallback strategy from manual to auto-generated subtitles, which is a behavioral trait. However, it does not explain what 'cleans' entails, potential failure modes, or the output format.

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 two sentences, directly addressing the core function and the fallback behavior without extraneous information.

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 the tool's simplicity (one parameter) and the presence of an output schema, the description is largely complete. It covers the primary functionality and fallback, though it could mention limitations like availability or language support.

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?

The schema provides only a parameter named 'url' with no description. The tool description clarifies that this parameter expects a YouTube video URL, adding essential meaning that the schema lacks.

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 fetches and cleans YouTube transcripts using yt-dlp, with a specific verb and resource. It also specifies fallback behavior, making it distinct and purposeful even without siblings.

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?

While there are no sibling tools to differentiate from, the description implies usage for YouTube video transcript retrieval. It does not explicitly state when not to use it, but the context is clear enough to guide an agent.

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