import_generated_asset_hunyuan

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

With no annotations, the description carries full burden but only states that the tool imports and returns success. It does not disclose side effects, prerequisites (e.g., completed generation), or error behavior. This is insufficient for a mutation tool.

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 concise with two sentences and a parameter list. It is front-loaded with the purpose. Some structural improvements (e.g., clearer separation) could enhance readability, but it is efficient.

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 simple import tool with 2 parameters and no output schema, the description covers the essential information. However, it lacks details on failure scenarios, asset conflicts, or integration steps, leaving some gaps.

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?

Despite 0% schema coverage, the description adds clear meaning for both parameters: 'name' is the object name in scene, and 'zip_file_url' is from the generate model step. This compensates well for the lack of schema 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?

The description clearly states the tool imports an asset generated by Hunyuan3D after generation. It distinguishes from sibling import_generated_asset by specifying the source as Hunyuan3D.

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 mentions 'after the generation task is completed' and that zip_file_url comes from the generate step, which offers some usage context. However, it does not explicitly differentiate when to use this tool versus the generic import_generated_asset or other siblings.

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