transcribe_youtube

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 mentions the pipeline but lacks details on destructiveness (e.g., temporary file deletion), required permissions, supported languages, max duration, or error handling. 'STT-first' is unclear.

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 a single sentence that is highly concise and front-loaded with the verb and resource. Every word serves a purpose without redundant 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 multi-step complexity (download, normalize, transcribe) and lack of annotations, the description is too brief. It omits critical details like output format, audio length limits, or language support, making it incomplete for agent decision-making.

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 input schema has 0% description coverage, and the description does not add meaning beyond the parameter name 'url_or_video_id'. It fails to explain required format (full URL vs ID) or provide examples, leaving agents with insufficient 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?

The description clearly states the action sequence (download, normalize, transcribe) and the resource (YouTube video). It distinguishes from sibling tools like 'download_youtube_audio' (just download) and 'transcribe_audio' (transcribe audio without YouTube step), making the purpose specific and unambiguous.

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 implies usage for transcribing YouTube videos but provides no explicit guidance on when to use this tool over siblings (e.g., if audio is already obtained, use 'transcribe_audio'), and does not mention prerequisites or context.

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