download_clip

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

No annotations are provided, so the description must fully disclose behavior. It specifies the download location and return values, but doesn't mention potential side effects (e.g., whether the server copy is deleted), authentication needs, or error handling. For a simple download, this is adequate but lacks depth.

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 three concise sentences with no wasted words. It front-loads the action and returns, then adds usage conditions. Every sentence contributes meaning.

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 adequately specifies the return value (file path and size). It covers the required parameters sufficiently. However, it could mention error scenarios or file format details, but is reasonably complete for a simple download tool.

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 schema description coverage at 0%, the description adds some value by clarifying that clip_index is 1-based. However, it doesn't explain job_id beyond being a string, and both parameters lack any format or example details. The description partially compensates for the missing schema descriptions.

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 action ('Download a rendered clip'), the target location ('local Downloads folder'), and the return value ('file path and size'). It distinguishes itself from sibling tools like clip_video (which creates clips) and get_clip_status (which checks status).

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?

Explicitly states when to use: after get_clip_status reports completion, with the correct clip_index. Also gives a clear prohibition: 'Don't call this for jobs that are still processing.' This provides excellent guidance.

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