import_generated_asset_hunyuan

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

No annotations are provided, so the description must disclose behavioral traits. It only states it imports and returns success, omitting details like destructiveness, side effects, or error handling. This is insufficient for a tool with no annotations, leading to a low score.

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 and front-loaded, stating the main action first. It covers parameters and return value in a few sentences without fluff. Every sentence serves a purpose.

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 tool with 2 required parameters and no output schema, the description covers the essentials: purpose, when to use, parameter meanings, and return. However, it lacks error handling context and prerequisites (e.g., generation must be complete). Still, it is largely complete for the tool's complexity.

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?

The schema has 0% description coverage, so the description adds value. It explains that 'name' is the object name in scene and 'zip_file_url' is from the generate step, which goes beyond the schema's minimal titles. This provides meaningful context, earning a 4.

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 it imports an asset generated by Hunyuan3D after task completion, making the purpose clear. It distinguishes from download/generate tools, but there is a sibling 'import_generated_asset' without Hunyuan suffix, which could be confusing. The mention of 'Hunyuan3D' provides specificity, earning a 4.

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 says 'after the generation task is completed' and references the zip_file_url from the generate step, giving context on when to use. However, it does not explicitly say when not to use or mention alternatives, such as the generic import_generated_asset tool. Thus, it is adequate but not thorough.

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