import_generated_asset_hunyuan

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

No annotations provided; description lacks details on side effects, required permissions, or impact on scene. Does not disclose whether import overwrites existing objects or creates new ones, nor any irreversible actions.

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?

Two sentences: one for purpose, one for parameters. Efficient but could be better structured (e.g., separate lines). No unnecessary content.

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?

No output schema and no annotations. Description does not specify return value, prerequisites beyond generation, or what happens to existing assets. Incomplete for a mutation tool with no annotations.

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 coverage is 0%, but description adds meaning: 'name: object name' and 'zip_file_url: from the poll step when status is DONE'. This clarifies parameter sources beyond the schema's minimal titles.

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?

Tool name and description clearly indicate importing a Hunyuan3D generated asset after generation. Specific verb 'import' and resource 'generated asset' with context of completion. Distinguishes from sibling tools like 'generate_hunyuan3d_model' and 'import_generated_asset'.

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?

Description states 'after generation completes' and references 'poll step when status is DONE', providing clear usage context. Does not explicitly list alternatives or when not to use, but the context is sufficient given sibling tools.

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