create_character_mesh

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 does not disclose whether this is a long-running job (and whether request_id is for idempotency/polling), what permissions or project state are required, or what side effects the creation has on the source version. For a mutation tool with zero annotation coverage this is a significant gap.

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, so nothing is wasted. However, it is under-specified rather than genuinely concise — the brevity leaves the core behavioral and parameter questions unanswered.

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 described, but for a 5-parameter creation tool with no annotations and 0% schema coverage, the description omits the pipeline context, prerequisites, and parameter meanings an agent needs to invoke it correctly.

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 5 parameters, and the description only hints at source_version via 'from one exact character version.' It says nothing about project_root, character_id, request_id (likely an idempotency/dedup key), or subdivision_levels, leaving four required/optional parameters unexplained in both schema and prose.

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 resource ('create a mesh version') and adds the scoping detail 'from one exact character version,' which separates it from create_character and retopologize_character. It does not explicitly name a sibling alternative, but the resource is distinctive enough that an agent can place it.

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 guidance on when this step belongs in the character pipeline versus retopologize_character, create_uv_and_materials, or groom_character. The only implied condition is that a source character version must exist, which is inferred from 'from one exact character version' rather than stated.

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