retexture_model

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions the output format (new .glb path) but does not discuss side effects, synchronization, permissions, rate limits, or error conditions. For a mutation tool, this is insufficient.

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 concise (two sentences, 30 words) and front-loads the primary purpose. Every sentence adds essential value without 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 6 parameters (0 required), no output schema, and no annotations, the description is incomplete. It lacks details on parameter behavior, synchronization model, error handling, and constraints, which are critical for correct tool invocation.

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%, meaning the description adds no parameter documentation beyond the schema's property names. While it groups parameters into source identifiers and style descriptors, it fails to explain parameters like enable_pbr or timeout, leaving their semantics unclear.

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 action ('re-texture'), the resource ('existing model'), and the outcome ('new variant'). It also specifies the valid sources (input_task_id or model_url) and style inputs (text_style_prompt or image_style_url), making it unambiguous and distinct from sibling tools.

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 usage guidance by explaining how to identify the source model and describe the desired look. However, it does not explicitly state when to use this tool over alternatives (e.g., generate_3d_model, rig_model), nor does it mention when not to use it or any prerequisites.

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