unwrap_uv

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

Annotations are absent, so the description must explain behavior. It only says 'UV 展开' and lists methods, but does not disclose side effects, such as modifying existing UV maps, whether the object must be selected, or how the operation affects the mesh.

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 extremely terse (a single short sentence). While it avoids verbosity, it omits crucial information, making it too sparse to be considered well-structured or appropriately sized for a tool with 5 parameters.

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 the tool has 5 parameters, no schema descriptions, and no output schema, the description is severely incomplete. It does not explain the overall purpose beyond the tool name, nor does it cover parameter usage, prerequisites, or results.

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?

The description only mentions the method parameter by listing its enum values, but provides no explanation for margin, uv_map, or angle_limit. With 0% schema description coverage, the description fails to compensate for the missing parameter meanings.

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 tool's purpose as 'UV 展开' (UV unwrap) and lists the available methods (ANGLE_BASED, CONFORMAL, etc.), making it distinct from sibling tools like pack_uv_islands or mark_seams.

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 is provided on when to use this tool versus alternatives such as pack_uv_islands, mark_seams, or add_uv_map. The description only lists method names without explaining their appropriate use cases.

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