generate_hunyuan3d_model

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

With no annotations, the description carries full burden. It discloses asynchronous behavior (returns job_id, status changes to DONE) and built-in materials. However, it does not detail potential side effects on the Blender scene (e.g., overwriting existing objects).

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 fairly concise, with a clear header, parameter list, and return section. It front-loads the main purpose. Could be slightly more compact but no wasted sentences.

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?

Given the tool's complexity (async generation, import) and lack of output schema, the description covers purpose, parameters, and return behavior (job_id, status, error). It lacks details on import semantics (e.g., whether it replaces or adds to scene) and how to poll status, but is largely adequate.

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 description compensates well. It clarifies text_prompt as optional and input_image_url as optional with URL format ('local or remote url') and the ability to accept None if only text is used.

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 explicitly states 'Generate 3D asset using Hunyuan3D' and 'import the asset into Blender', using a specific verb and resource. It distinguishes from sibling tools like generate_hyper3d_model_via_text by specifying Hunyuan3D and built-in materials.

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 providing text, image, or both, but does not explicitly state when to use this tool over alternatives (e.g., hyper3d generators or separate import tools). Usage context is implied but lacks exclusions or explicit guidance.

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