generate_hunyuan3d_model

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

With no annotations, the description carries the full burden. It discloses the asynchronous behavior via 'job_id' and status change to 'DONE', mentions built-in materials, and describes error handling. It does not mention prerequisites like Blender running or potential side effects, but the core workflow is well conveyed.

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 a summary, a parameters list, and a returns section. It is concise, with every sentence adding value. The front-loaded purpose makes it easy to scan.

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 main flow: input, generation, import, and return values. It does not explain how to check the job status (though a sibling poll tool exists) or discuss timeouts, but for a tool with no output schema and moderate complexity, it is quite 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%, so the description must compensate. It explains text_prompt and input_image_url, including that image accepts None for text-only. However, it omits the user_prompt parameter entirely, leaving it unexplained. This is a partial compensation with a clear gap.

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 by providing either text description, image reference, or both for the desired asset, and import the asset into Blender.' This specifies the verb, resource, and action. It also distinguishes from siblings like generate_hyper3d_model_via_text by naming the Hunyuan3D model 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 explains the inputs ('providing either text description, image reference, or both') and notes that the asset is imported into Blender, but it does not explicitly compare this tool to alternative generation tools (e.g., generate_hyper3d_model_via_text) or state when to prefer one over the other. Usage context is implied but no exclusion or alternative is named.

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