Ytdlp Remux

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

Description discloses the core behavior: uses ffmpeg, defaults to MP4, no re-encoding. Annotations indicate it is not read-only and has open-world side effects. However, it does not detail potential side effects like network usage or disk space, and the description adds moderate context beyond 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?

The description consists of two sentences with no fluff. It front-loads the action and use case, making it efficient for the agent to parse.

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, many siblings, output schema exists), the description is adequate but minimal. It covers the basic function and when to use, but does not elaborate on parameter effects or outputs (though output schema helps). It could be more complete with typical usage examples.

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 only explains the url parameter (media URL) and the output container (MP4). With 13 parameters including many nested objects, the description fails to add meaning to the vast majority of parameters, leaving the agent to infer from property names.

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 a media URL and remuxes the container with ffmpeg to MP4 without re-encoding. It specifies the verb 'download and remux', the resource (media URL), and the output format (MP4), distinguishing it from siblings like ytdlp_recode (re-encodes) and ytdlp_download_video (downloads only).

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 says to use when the user asks to convert containers like MKV/WebM to MP4. This provides clear positive guidance, though it does not explicitly mention when not to use or contrast with alternatives like recode or download audio.

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