Ytdlp Extract Audio

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

The description mentions using ffmpeg/ffprobe for extraction, giving a hint about dependencies, which adds value beyond the annotations that indicate it is mutable and non-idempotent. However, it does not disclose that ffmpeg must be installed or that output files are saved somewhere, leaving gaps in understanding the tool's side effects.

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 exceptionally concise with two sentences. The first sentence states the core purpose, and the second provides usage guidance. No unnecessary words or repetition; it earns its place.

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 (13 parameters, nested objects, output schema), the description is far too sparse. It does not describe return values, how to control format selection, or handle authentication and output options. The usage tip is helpful but insufficient for an agent to use all features correctly.

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?

With 0% schema description coverage and 13 parameters (including nested objects), the description only implies the url parameter. It provides no guidance on how to use other important parameters like format, output, or postprocess, which are critical for controlling the extraction behavior.

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 (download and extract audio) and resource (media URL). It lists specific audio formats (MP3, M4A, Opus, WAV) which helps distinguish from video download or other audio tools, though it could be more explicit about differences from ytdlp_download_audio.

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 instructs to use when the user asks for common audio formats or audio-only output. It does not mention when not to use it or alternative tools, but for a straightforward extraction tool, the guidance is clear and actionable.

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