Ytdlp Download Video

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

Discloses default format selection ('bestvideo*+bestaudio/best') and that it creates local files under output root. Annotations already indicate non-read-only and non-idempotent, so description adds value without contradiction.

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?

Description is concise with purpose first, then usage guidelines, and a note on default behavior. No 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 complexity (14 parameters, many nested), the description covers core usage but lacks details for the extensive parameter options. Output schema exists but description doesn't reference it.

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 description provides only high-level mention of 'trim sections' and 'overwrite behavior' without detailing the numerous nested parameters. Does not compensate sufficiently for the missing 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?

Description clearly states 'Download a web video URL to the managed output root' with specific examples (YouTube, youtu.be). It distinguishes from sibling tools like ytdlp_download_audio by focusing on 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?

Explicitly lists 'Use when' (download, save, best quality, format requests, trim, overwrite) and 'Don't use when' (audio, subtitles, thumbnails, metadata, dry-run). Provides clear alternatives.

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