create_image_to_3d_task

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

With no annotations, the description carries the full behavioral burden and does add useful details: accepted image input formats, allowed enum values, and the effect of skipping texturing. However, it does not disclose that this is likely an asynchronous task creation endpoint, what it returns, or any auth/rate-limit/cost behavior.

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 front-loaded with the core action and then compactly enumerates key constraints without filler. It is dense but appropriately sized for a 14-parameter tool, though it could be more scannable if structured.

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 14-parameter creation tool with no annotations and no output schema, the description is incomplete: it omits task lifecycle details, expected return behavior, and half the parameters. An agent can make a basic call but lacks enough context to use the tool reliably across its full option set.

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% across 14 parameters, so the description must compensate. It explains 7 parameters including image_url format constraints and enum values for ai_model, topology, symmetry_mode, pose_mode, and origin_at, but leaves auto_size, enable_pbr, should_remesh, target_formats, texture_prompt, target_polycount, and texture_image_url undocumented.

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 states a specific verb and resource: generate a 3D model from an input image. It is clear enough to distinguish from text-to-3D, but it does not explicitly differentiate from sibling tools like create_multi_image_to_3d_task or name alternatives.

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?

There is no explicit guidance on when to use this tool versus create_text_to_3d_task, create_multi_image_to_3d_task, or the streaming/retrieval siblings. The mention of should_texture=false is a parameter behavior note, not a when-to-use guideline.

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