generate_hunyuan3d_model

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

No annotations are provided, so the description carries the full burden. It discloses the asynchronous nature (returns job_id, status changes to DONE), the auto-import into Blender, built-in materials, and error handling. It does not cover rate limits or authentication, but these are less critical for a generation tool. Overall, it provides solid transparency.

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 well-structured with Purpose, Parameters, and Returns sections. Every sentence adds value, with no fluff or redundancy. It is appropriately sized for the tool's complexity.

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?

The description covers the full workflow: generation, import, job status, and success criteria. It includes return format and error handling. It could explicitly mention that the agent may need to poll for status, but the job_id and status change description imply this. Given two optional parameters and an output schema, this is nearly complete.

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%, and the description fully compensates by explaining each parameter: text_prompt is optional, short, and supports English/Chinese; input_image_url accepts local or remote URLs and None when only using text. This adds meaningful usage guidance beyond the raw 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's purpose: 'Generate 3D asset using Hunyuan3D' with input options (text/image/both) and import into Blender. It distinguishes itself from sibling tools like generate_hyper3d_model_via_text/image by naming Hunyuan3D explicitly and emphasizing the import behavior.

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?

Usage context is well implied: the tool should be used when generating a new Hunyuan3D asset from text or image. It describes the optional inputs but does not explicitly state when not to use it or point to alternatives (e.g., polling tools for status checks). The mention of job_id and import behavior gives clear context for the generation workflow.

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