create_text_to_texture_task

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the endpoint is actually /v1/retexture and how parameters are remapped, which is valuable. However, it omits that this is an asynchronous task-creation operation and says nothing about permissions, cost, or lifecycle.

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?

Purpose is front-loaded, followed by the alias caveat and parameter-mapping notes. Sentences are dense and mostly earn their place, though the forwarding detail is slightly verbose relative to what's explained.

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 an 8-parameter, no-annotation, no-output-schema mutation tool, the description covers the tricky mapping and required param but leaves three parameters undocumented and never clarifies the async task semantics. Adequate but with clear gaps.

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 coverage is 0% across 8 parameters, so the description must compensate. It explains model_url is required, the style_prompt/object_prompt aliasing, and enable_original_uv/enable_pbr forwarding, covering several params. But art_style, resolution, and negative_prompt are left completely 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?

States a clear verb and resource: 'Apply textures to a 3D model using text prompts.' It also reveals it's a compatibility alias backed by the retexture API, which meaningfully distinguishes it from the plain retexture siblings. It stops short of explicitly directing agents between this and create_retexture_task.

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 'Compatibility alias' framing implies this exists for backward compatibility and uses the retexture endpoint, but it never states when to prefer this over create_retexture_task or what input conventions differ. Usage context is implied rather than explicit.

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