download_to_storage

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

Annotations are all false, so the description carries responsibility for behavioral disclosure. It adds meaningful context beyond schema: the wait parameter controls whether the tool returns a UPID (async task) versus a completed result, and checksum support is explained. It does not describe overwrite behavior or permission requirements, but the core async behavior is disclosed.

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 clear purpose sentence followed by a compact Args list. Every line adds value, with examples for filename and algorithm enumerations, and no fluff.

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?

Coverage is strong for a 7-parameter tool with an output schema: all inputs are defined, the async wait behavior is highlighted, and the output schema handles return values. No major behavioral gaps remain.

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 0%, but the description documents each of the 7 parameters with types, examples, allowed values, and defaults. This fully compensates for the schema gap.

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 opens with a specific verb phrase 'Download an ISO or container template straight to a storage', clearly stating the operation and target. The parameter list reinforces the exact purpose and differentiates it from sibling tools like list_storage or storage_content.

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 clear context: it is for downloading ISOs or container templates to storage, with typical storage 'local'. It doesn't explicitly name alternative tools or when-not-to-use, but the purpose is narrow enough that an agent can infer appropriate usage.

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