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 that the operation is asynchronous (returns job_id, status changes to 'DONE'), mentions failure cases, and notes built-in materials. However, it lacks details on permissions, rate limits, timeouts, or what 'import into Blender' entails operationally. The behavioral context is partial but not comprehensive.

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 appropriately sized and front-loaded: the first sentence states the core functionality. The parameter and return sections are structured but slightly verbose (e.g., repeating 'When successful...'). Most sentences earn their place, though some redundancy exists in the returns explanation.

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 no annotations, 0% schema coverage, no output schema, and moderate complexity (asynchronous 3D generation), the description is partially complete. It covers purpose, parameters, and return behavior but lacks details on error handling, Blender integration specifics, and sibling differentiation. It's adequate but has clear gaps for a tool with this scope.

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 meaningful semantics: text_prompt is described as 'a short description of the desired model in English/Chinese,' and input_image_url as 'local or remote url' that 'Accepts None if only using text prompt.' This clarifies optionality and format beyond the bare schema. However, it doesn't cover constraints like image size or prompt length.

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' and 'import the asset into Blender.' It specifies the input modalities (text, image, or both) and mentions built-in materials. However, it doesn't explicitly differentiate from siblings like 'generate_hyper3d_model_via_images' or 'import_generated_asset_hunyuan' beyond the Hunyuan3D reference.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'generate_hyper3d_model_via_text', 'generate_hyper3d_model_via_images', and 'import_generated_asset_hunyuan', there's no indication of comparative use cases, prerequisites, or exclusions. Usage is implied by the description but not explicitly stated.

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