generate_hyper3d_model_via_images

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

With no annotations, the description bears full responsibility. It discloses that the model has built-in materials, is normalized, and returns a success/failure message. However, it lacks details about potential side effects, such as whether the tool blocks until completion, or if it requires network access for FAL_AI mode.

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 introductory statement followed by parameter explanations. It is somewhat lengthy but every sentence adds value. Minor improvement could be to bullet the parameter details more concisely.

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 + import) and no output schema, the description explains the basic process and result. However, it does not clarify how the import step works (e.g., auto-import vs separate tool) or whether the generation is asynchronous, which is implied by the existence of sibling tools for polling status.

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 explain parameters. It clearly adds meaning: input_image_paths must be absolute paths and even single image requires a list; input_image_urls similarly; bbox_condition optional with specific format. This fully compensates for the lack of schema descriptions.

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 distinguishes itself from the text-based sibling (generate_hyper3d_model_via_text) by specifying images as input.

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 explicit guidance on when to use input_image_paths vs input_image_urls depending on the Hyper3D Rodin's mode. It also notes that the model is normalized and may need rescaling. However, it does not explicitly state when to prefer this tool over text-based generation or other alternatives.

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