meshy_download_workflow

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

Annotations already indicate idempotent and non-destructive behavior, so the description adds value by disclosing a critical cost-related behavior: 'submits no paid tasks'. It also clarifies the concrete side effect of downloading artifacts into the saved run directory.

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 one sentence with the action front-loaded and the important cost/side-effect qualifier appended. Every word contributes meaning, and there is no filler or repetition of schema details.

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 one-parameter tool with an output schema, the description covers what is downloaded, where it goes, and the non-billing behavior. It could explicitly say that the workflow must be completed before calling, but 'completed model' sufficiently implies the prerequisite.

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 the description must compensate. It clarifies that run_dir is the 'saved run directory' and the destination for downloaded artifacts, but it does not specify whether the directory must already exist or how it is resolved. For a single self-named parameter, this is minimally acceptable.

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 states a specific verb and object: download completed model and texture artifacts into the saved run directory. It also explicitly distinguishes itself from paid task submission with 'submits no paid tasks', separating it from siblings like meshy_start_multiview and meshy_advance_workflow.

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 phrase 'completed model and texture artifacts' gives clear context that this is the retrieval step after a task has finished, and 'submits no paid tasks' tells agents when not to use it. It does not explicitly name alternative sibling tools, but the distinction from submission-oriented siblings is clear.

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