generate_hunyuan3d_model

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

With no annotations provided, the description clearly discloses the asynchronous workflow (returns job_id, status changes to DONE), the import action, and error handling. It adds context beyond the schema, though it does not cover side effects like overwriting or permissions.

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 clear sections and bullet points. It is front-loaded with the main purpose and efficiently covers parameters and return values, though it could be slightly more concise.

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 (asynchronous generation, no annotations) and two optional parameters, the description provides sufficient context: input options, return format, and job lifecycle. It lacks details on combined text+image behavior and error message formats, but is adequate for an agent.

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%, but the description adds meaningful semantics: text_prompt is a short description in English/Chinese, input_image_url accepts local/remote URL or None. This compensates well for the lack of schema descriptions.

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 or image and imports it into Blender. It distinguishes from siblings by naming the specific engine (Hunyuan3D vs Hyper3D) and mentioning import into Blender, which is unique among the generation tools.

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 input options (text and/or image) but provides no guidance on when to use this tool versus alternatives like generate_hyper3d_model_via_text or get_hunyuan3d_status. It does not specify prerequisites or when not to use it.

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