import_generated_asset_hunyuan

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the import action; it does not disclose that this mutates the scene, downloads and extracts the ZIP, requires a completed generation, or what it returns or does on failure.

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 sentence with no fluff and the source qualifier front-loaded. It is concise and readable, though somewhat too terse to carry the missing behavioral and usage context.

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 two-parameter, no-nested, no-output-schema import tool whose schema is fully self-descriptive, this is minimally usable: an agent can infer to pass a name and a ZIP URL from the Hunyuan generate step. However, with no annotations and no mention of return behavior or prerequisites, it is not rich enough to fully handle failure cases or pipeline sequencing.

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 100%, so the baseline is 3. The description itself adds no parameter meaning beyond the schema, which already documents name as 'Object name in scene' and zip_file_url as 'ZIP file URL from generate step'.

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 ('Import') and a clearly bounded resource ('asset generated by Hunyuan3D'). This immediately distinguishes it from the generic sibling import_generated_asset and from the download/generation tools in the same family.

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 'generated by Hunyuan3D' implies this is for assets produced by the Hunyuan pipeline, as opposed to Polyhaven, Sketchfab, or Hyper3D assets. However, it never explicitly says when to call this versus import_generated_asset, nor does it state any prerequisites such as completing a prior generate_hunyuan3d_model step.

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