generate_3d_from_image

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

No annotations provided. The description details parameters and their effects (e.g., background removal, resolution trade-off) but does not disclose potential side effects (e.g., file overwriting), permissions, or error conditions. It adds value beyond the schema but lacks full behavioral disclosure.

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?

Description is efficient: a short purpose statement, a prerequisite sentence, and a bulleted parameter list. No redundant information; all sentences add value. Well-structured for quick parsing.

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 absence of an output schema and moderate complexity (5 params, 1 required), the description covers purpose, prerequisites, and all parameters. It does not explicitly describe the return behavior (e.g., path to generated file), but generating a .glb file is implied. Slightly more detail on output 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 fully compensates by explaining each parameter (image_path, output_path, foreground_ratio, mc_resolution, no_remove_bg) with meanings, defaults, and optionality. This is highly informative for an agent.

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?

Clearly states the tool generates a 3D mesh (.glb) from a single image using the local TripoSR model. This specific verb+resource combination distinguishes it from sibling tools for other 3D generation methods (e.g., generate_hunyuan3d_model, generate_hyper3d_model_via_images).

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?

Explicitly states a prerequisite: 'You must call load_img_to_3d_model() first.' This provides clear when-to-use guidance. However, it does not mention alternatives or when not to use this tool, though the prerequisite effectively implies the required context.

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