Ytdlp Recode

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

Annotations indicate write, non-idempotent, non-destructive behavior. The description adds the default MP4 output but doesn't discuss overwrite policies, performance implications, or further side effects. Consistent with annotations, but minimal added value.

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 two sentences, front-loads the verb and resource, and contains no extraneous information. Every word 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 (many nested parameters, output schema present), the description is too brief. It fails to guide the agent on configuration fields like format selection, output options, or network settings, which are critical for correct invocation.

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 complex nested parameters, the description offers no explanation of any parameter, leaving the agent to infer from the schema alone. This is insufficient for effective use.

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 and re-encodes media, defaulting to MP4, which distinguishes it from siblings like ytdlp_download_video (no re-encoding) and ytdlp_remux (container change 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?

The description specifies 'Use when the user asks for a target video format and accepts re-encoding,' giving clear context. However, it lacks explicit mention of when not to use or alternatives like ytdlp_download_video for direct downloads.

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