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 return format (JSON with job_id, status changes) and mentions built-in materials, but does not address potential side effects (e.g., scene modifications), authentication needs, or failure modes beyond 'error message'. The description is partially transparent but lacks depth.

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 reasonably concise with two paragraphs and a return section. While the parameter list is inline rather than formatted, there is no redundant information. It earns a 4 for efficient use of space.

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 (generation and import) and lack of output schema, the description covers key aspects: inputs, built-in materials, and workflow (job_id, status changes). However, it does not address polling mechanisms (sibling poll_hunyuan_job_status), expected duration, or scene impact, leaving some gaps 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 coverage is 0%, requiring the description to compensate. The description explains text_prompt and input_image_url, adding context beyond title/default, but omits the user_prompt parameter entirely. This incomplete coverage reduces effectiveness.

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 input and imports it into Blender. It uses the specific verb 'generate' and names the resource 'Hunyuan3D', distinguishing it from sibling Hyper3D 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 implies usage by stating the inputs (text, image, or both) but does not explicitly guide when to use this tool over alternatives like generate_hyper3d_model_via_text. It lacks exclusion criteria or prerequisites.

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