download_model

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

With no annotations provided, the description carries the burden and does it well: it discloses local STL conversion, default longest edge 100 mm, loss of color/texture, GLB passthrough, and the parent-directory prerequisite. It stops short of describing overwrite behavior, error cases, or return values, but the core side effects are transparent.

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?

Three tight sentences with no wasted words. The most important information—what the tool does, the id source, and format behavior—is front-loaded, and each sentence contributes distinct value.

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 annotations and no output schema, the description covers the essential invocation context: source of id, formats, defaults, and a filesystem prerequisite. Minor gaps remain around success/failure behavior and overwrite semantics, but an agent can call this correctly with the provided information.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains what each format does, clarifies that id is a task id rather than an assetId, and notes that parent directories must exist. This goes beyond the schema's terse property 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?

States a specific verb and resource: 'Download a completed generation to a local path.' It also disambiguates the id from an upload assetId, which distinguishes this tool from upload_image and other generation-related siblings. The purpose is immediately actionable.

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?

Clear context is given: the tool is for completed generations and requires a local destination path. It explicitly says id comes from generate_model/get_task and is not an upload assetId, providing a useful exclusion. It does not explicitly name alternatives, but the guidance is sufficient for an agent to route correctly.

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