Ytdlp Download Audio

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that it creates local audio files under the configured output root, confirming the write behavior. While it doesn't detail side effects like overwriting or auth requirements, the combination is adequate.

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 relatively short (three sentences plus lists) and front-loaded with purpose. However, listing audio formats (MP3, M4A, etc.) is somewhat redundant with the schema's audioFormat enum but still helpful. Minor waste, but overall efficient.

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 high parameter count, nested objects, and 0% schema coverage, the description fails to provide sufficient context for proper usage. It does not mention required parameters, sample output, or how to configure audio format, leaving significant gaps despite an output schema existing.

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 has 14 parameters with 0% description coverage. The description does not describe any parameters, leaving the agent without guidance on how to use the complex nested schema, including required url and key audio format options.

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 downloads or extracts audio from a web URL, listing specific use cases like MP3, M4A, Opus, WAV, best audio, and podcast/music extraction. This differentiates it from sibling tools like ytdlp_download_video which handle 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?

Explicit 'Use when' and 'Don't use when' sections provide clear guidance on appropriate scenarios, including when to avoid (e.g., need video, subtitles only) and references to other tools without naming them explicitly but sufficiently.

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