Download a 3D model

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

Despite no annotations, the description discloses important behavioral trait: non-GLB formats are converted on demand, causing first request to take longer. It doesn't explicitly state non-destructiveness or auth needs, but the context of a download tool implies read-only. Slight deduction for missing explicit safety statement.

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 two clear sentences followed by a paragraph of context. No wasted words; the first sentence effectively summarizes the action and resource.

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 the presence of an output schema, the description need not detail return values. It covers when to use, format details, and conversion behavior. It could briefly mention what the tool returns (e.g., file path or data stream), but overall it is sufficiently complete for a straightforward 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?

Schema description coverage is 0%, so description should compensate. While it explains the 'format' parameter by listing examples (GLB, FBX, OBJ, STL, USDZ), it does not explain the required 'submission_id' or the optional 'dest' parameter. The description adds only partial meaning beyond the raw schema.

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 title and description clearly state the verb 'save' (or download) and the resource 'finished model', and the description distinguishes this from sibling tools like create_model or edit_model by noting that most tools auto-save GLB, so this tool is for alternative formats or re-downloading.

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: 'only need this to get a different format, or to re-save a model from an earlier session.' It implies when not to use (default GLB is auto-saved) and provides context on format availability and conversion behavior.

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