Ytdlp Download Playlist

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

Annotations already indicate non-readOnly (writes), non-destructive, open-world (side effects). The description adds context: downloads to 'managed output root', mentions archive handling and boundary behaviors like skip/stop. However, it doesn't elaborate on network usage, authentication, or exact file creation behavior beyond the existing annotations.

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?

Two sentences, no fluff. First sentence states core purpose, second lists specific use cases. Information is front-loaded and every word contributes. Ideal conciseness.

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, nested objects, output schema), the description covers some usage scenarios but lacks full parameter guidance. Output schema exists, so return values are covered, but the description could better map user intents to param structures. It's adequate but not exhaustive.

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%, so the description must compensate. It hints at several parameters (playlistItems, downloadArchive, maxDownloads, playlistRandom, breakOnExisting) by mentioning use cases. However, many parameters (auth, kind, format, output, network, etc.) are not addressed. The description adds value for a subset but not a majority.

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 specifies the tool's purpose: downloading playlist, channel, or multi-video entries. It distinguishes from sibling tools like ytdlp_download_video by explicitly targeting multi-item URLs. The verb 'download' and resource 'playlist/channel/multi-video' are precise.

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 explicitly states when to use this tool: when the user asks to download a playlist/channel, select ranges, skip existing, cap max, randomize, or stop on existing. It provides clear context but does not mention when NOT to use it or suggest alternatives like ytdlp_download_video for single videos.

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