generate_hyper3d_model_via_images

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

With no annotations, the description carries the full burden. It discloses that the generated model has built-in materials and normalized size, and that re-scaling may be useful. It also explains the bbox_condition parameter's effect. No destructive or safety issues mentioned, but the tool is generative and likely safe.

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 clear opening, behavioral notes, and bullet-pointed parameters. It is concise but could be slightly more streamlined. The parameter list is helpful.

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?

With 4 parameters, no output schema, and no annotations, the description covers basic usage but lacks details on the output format beyond a success/failure message. The import step is mentioned but not detailed. For a complex generative tool, more context on post-generation workflow would improve completeness.

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 explains input_image_paths, input_image_urls, and bbox_condition well, but fails to mention the user_prompt parameter, leaving it undocumented. This gap reduces clarity.

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 Hyper3D from images and imports it into Blender. It also mentions built-in materials and normalized size, distinguishing it from siblings like generate_hyper3d_model_via_text.

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 when to use input_image_paths vs input_image_urls based on the Hyper3D Rodin's mode. It does not explicitly list alternatives, but the sibling tool names provide context. The guidance is clear and actionable.

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