generate_hyper3d_model_via_images

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

No annotations are provided, so the description carries full burden. It mentions built-in materials, normalized size (with re-scaling suggestion), and that it imports into Blender. However, it does not disclose potential failures, time requirements, or async behavior (despite sibling poll_rodin_job_status hinting at async).

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 compact, front-loaded with the core purpose, and uses structured bullet points for parameters. Every sentence adds value without repetition.

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?

For a generation tool with two modes and import step, the description covers basics but omits how to determine the current mode, that generation may be asynchronous (given sibling polling tool), and the return value is vague ('message indicating success or failure'). No output schema exacerbates the gap.

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?

With 0% schema description coverage, the description adds significant meaning: absolute paths requirement, list wrapping for single images, bbox_condition length 3 and ratio control. These details are not in the schema, making the description valuable.

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 verb+resource: 'Generate 3D asset using Hyper3D by giving images' and notes import into Blender. It distinguishes from siblings like generate_hyper3d_model_via_text (text input) and import_generated_asset (import already generated).

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 that only one of input_image_paths or input_image_urls should be given depending on the Hyper3D Rodin's current mode, but does not explicitly say when to use this tool over alternatives or provide when-not conditions. The mode distinction is only partially explained.

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