generate_hunyuan3d_model

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

With no annotations provided, the description carries full burden. It discloses asynchronous behavior (returns job_id indicating task in progress), completion semantics (status changes to DONE when imported), error handling, and built-in materials. This goes beyond simple mutation and gives the agent an accurate picture of the tool's lifecycle.

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: a one-sentence purpose, a short note on materials, a focused parameter list, and a clear return/status list. Every sentence earns its place; no fluff or repetition of schema defaults.

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 (generation, async job, completion, import), which is good for a tool with no output schema. However, it could be more complete by referencing how to check job status (e.g., poll_hunyuan_job_status) and by documenting the missing user_prompt parameter. Given the tool's complexity, this is a minor gap but not fatal.

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%, so the description must compensate. It adds meaning for text_prompt and input_image_url, but entirely omits the third schema parameter 'user_prompt'. This is a significant gap: the agent knows how to fill two of three fields, but has no guidance for the third. Partial compensation, not complete.

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 states a specific verb ('Generate') and a specific resource ('3D asset using Hunyuan3D'), and explicitly notes the result is imported into Blender. This differentiates from sibling tools like generate_hyper3d_model_via_text and import_generated_asset_hunyuan.

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 clearly indicates the tool is used for generating Hunyuan3D assets from text and/or image, and that it also imports into Blender. While it doesn't explicitly mention alternatives or when not to use it, the context implies differentiation from Hyper3D generation tools and separate import tools. This meets 'clear context, no exclusions' level.

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