Download media

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

The description discloses key side effects: it writes a file, consumes significant bandwidth and storage, and requires authorization. This goes beyond the annotations and sets realistic expectations.

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 short sentences with no filler. It front-loads the main action and then notes the important side effects.

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 straightforward download tool with a fully described schema, the description provides enough context about the action, side effects, and authorization requirement. No output schema is needed for this simple operation.

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 schema already provides full descriptions for all four parameters, including the confirm_authorized flag. The tool description adds no per-parameter detail beyond what the schema covers, so the baseline of 3 applies.

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 complete media item locally in MP4 or MP3 format, which is specific and distinguishes it from clip-only or inspection tools.

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?

It conveys that the tool is for complete authorized media downloads and hints at the need for user confirmation, but it does not explicitly direct users to download_clip for partial clips or inspect_media for previews.

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