download_asset

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

No annotations are provided, so the description carries the full burden. It discloses that the tool works for all asset types, creates directories if missing, and notes the YouTube URL nuance. However, it does not mention overwrite behavior, error handling, or return values. Adequate but not rich.

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 efficient sentences. The first states the primary purpose, and the second adds a critical nuance about YouTube. No wasted words; front-loaded and to the point.

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 no output schema, the description should explain return values (e.g., saved file path, success status). It does not. It also omits error cases or prerequisites beyond the URL source. While it covers core functionality well, the lack of return value documentation is a notable gap.

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 100%, so the schema already documents all three parameters. The description adds context that 'url' is from search_broll and that 'dir' is absolute and created if missing, but this does not significantly exceed what the schema provides. Baseline 3 is appropriate.

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 single asset URL to a local file for timeline use, and specifies it comes from search_broll's download_url. It distinguishes from siblings like build_premiere_script, build_timeline, and place_in_resolve, which handle other stages of asset processing.

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 gives context that all asset types are downloadable and adds a specific note about YouTube (page_url for moving clips). It implies usage after search_broll but lacks explicit when-not-to-use or alternative tool guidance. Clear context but no exclusions.

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