generate_hunyuan3d_model

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

With no annotations, the description discloses the asynchronous workflow (returns job_id, status DONE), built-in materials, and error handling. It does not mention potential side effects on the Blender scene or timeout behaviors, but covers the essential behavioral traits.

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 with the main purpose. It uses clear paragraphs and a bullet-like list for parameters. Minor improvement could be formatting the parameters more explicitly.

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 async generation and import workflow, the description covers input options, job_id return, status progression, and error messages. It mentions the need to poll for completion, and a sibling polling tool exists. No output schema, but return behavior is described adequately.

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 the description explains that text_prompt should be a short English/Chinese description and input_image_url accepts local/remote URLs, with None allowed for text-only generation. This adds meaning to the bare schema.

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 generates a 3D asset using Hunyuan3D from text, image, or both, and imports it into Blender. It distinguishes from siblings like generate_3d_from_image by specifying the Hunyuan3D service and the import step.

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 implies usage for generating 3D assets from text/image but does not explicitly state when to choose this over similar tools like generate_hyper3d_model_via_images or generate_3d_from_image. No prerequisites or exclusions are mentioned.

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