retexture_create

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states inputs, not whether the tool is asynchronous, what happens on success/failure, or any side effects. This is insufficient for an agent to fully anticipate the tool's 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 a single, clear sentence front-loaded with the purpose, followed by the key usage constraint. Every phrase earns its place with no redundancy.

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 9 parameters and no required fields, the description omits critical context: the tool likely initiates an asynchronous task (based on sibling names like wait_for_task), returns a task ID, and may have error conditions. Without output schema or further description, an agent cannot fully plan its use.

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 100%, so the baseline is 3. The description adds value by grouping parameters logically, but does not explain each parameter beyond the schema's individual descriptions. Minimal extra meaning provided.

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 clear verb and resource ('Apply new textures to a 3D model') and distinguishes the tool from siblings like image_to_3d_create or remesh_create by emphasizing retexturing. It also notes the two alternative input methods.

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 clear instructions on required parameter groups ('Provide either input_task_id or model_url, and either text_style_prompt or image_style_url'), but does not specify when to use this tool versus other texturing-related tools or mention prerequisites or when not to use it.

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