AI Download

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

Annotations already supply the safety profile (idempotentHint=true, destructiveHint=true, openWorldHint=true), so the bar is lower. The description adds that both image and video generations are supported, but it never explains the destructive aspect implied by destructiveHint — namely that writing to outputPath can overwrite an existing local file — nor what happens if the generation is not finished.

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?

A single front-loaded sentence with no waste; the verb, resource, and destination all appear immediately. It is perhaps slightly under-specified rather than verbose.

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 two-parameter, no-output-schema tool the definition is minimally viable, but it omits the meaning of 'id', any preconditions about generation completion, and the overwrite behavior that the destructive annotation implies.

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 only 50%: outputPath is well documented in the schema, but 'id' has no description in either the schema or the tool description. The parenthetical '(image or video)' loosely gestures at file type but adds nothing beyond the schema's existing extension guidance.

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?

States a specific verb (Save) and resource (a finished AI generation, image or video) written to a local file, which distinguishes it reasonably well from the clip-oriented download siblings like download_clip and download_beat_edit. It stops short of explicitly naming which sibling it supersedes.

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 word 'finished' implies the generation must be complete before calling (i.e., after ai_status reports done), which is useful implied guidance, but there is no explicit when-not statement and no routing to or away from download_clip/download_all_clips.

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