create_uv_and_materials

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

No annotations are provided, so the description carries the full burden. It hints at versioning by saying a 'new look-development version' is created, but it does not state whether the operation is idempotent, what happens if a version already exists, what permissions are needed, or how long it takes.

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?

A single efficient sentence with the action front-loaded and no filler. It is arguably too terse for the number of parameters it hides, but nothing in the sentence is wasted.

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?

An output schema exists, so return values need not be explained, but for a 6-parameter mutation tool with no annotations the description leaves the key inputs and their semantics entirely unexplained. An agent could not determine what source_version or request_id mean from this text alone.

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?

Six parameters with 0% schema description coverage, and the description names none of them. The required project_root, character_id, source_version, and request_id are completely undocumented, and the optional roughness/base_color are only obliquely implied by the word 'material'.

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 specific verb and two resources ('create UVs and a material') plus the destination context ('a new look-development version'), which distinguishes it from retopologize_character or groom_character. However, it gives no explicit sibling differentiation, so an agent must infer the pipeline position.

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?

No guidance on when this step should be run relative to siblings such as retopologize_character, rig_character, or promote_version, and no stated prerequisites. The agent is left to infer that a source_version must already exist.

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