download_stream

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

No annotations are provided, so the description must fully disclose behavioral traits. It only restates the action ('Download') without mentioning any consequences such as prolonged execution for live streams, resource usage, or dependency on ffmpeg. This is a significant gap for a streaming download tool.

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 a single sentence that is front-loaded with the core action and target. It is concise with no wasted words, making it easy to scan. It could be slightly longer to include behavioral context, but as written it is 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?

For a tool with 7 parameters, no annotations, and no output schema, the description is too minimal. It does not explain how to handle live streams (e.g., needing a duration to stop capture) or the meaning of advanced options like additionalArgs. An agent may struggle to call this tool correctly without additional context.

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?

The description does not mention any parameters, but the input schema provides descriptions for all 7 parameters with 100% coverage. The schema already explains fields like duration and outputName, so the baseline of 3 is appropriate. The description adds no extra meaning beyond the schema.

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 states a clear action ('Download') and a specific target ('a live stream or m3u8/HLS stream'), and mentions the underlying tool yt-dlp. It distinguishes itself from sibling tools like download_video by specifying stream types, though it does not explicitly name that sibling. The purpose is immediately understandable.

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 implies usage for live or HLS streams, which gives some guidance. However, it provides no explicit 'when to use this vs. alternatives' or exclusions, leaving the agent to infer that download_video is for regular videos. The guidance is present but implicit.

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