uv-smart_unwrap

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

With no annotations provided, the description carries full burden for disclosing behavioral traits. It does not mention side effects such as modifying existing UVs, auto-creating seams, or whether the operation is destructive. The phrase 'Smart UV project' implies it may alter UV layout but lacks specifics.

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, one sentence, and front-loaded with the core purpose. It earns its place without unnecessary filler, though it could benefit from slightly more detail given the tool's complexity.

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?

For a tool with three parameters and no annotations, the description is incomplete. It does not cover usage scenarios, parameter behavior, or operational details, leaving an agent with insufficient context to decide when and how to use it effectively.

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%, so the description must compensate. It does not mention any of the three parameters (object, angle_limit, island_margin) or their roles, although the schema titles provide some basic semantics. The mention of 'angle-based' hints at angle_limit but does not explain the other parameters.

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 action ('Smart UV project') on a specific resource ('the selected faces') and hints at the approach ('angle-based auto seams'), which helps distinguish it from sibling tools like uv-unwrap or uv-cube_project. However, it could be more explicit about what 'smart' entails.

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 like uv-unwrap or other projection methods. The description does not mention any prerequisites, selection requirements, or scenarios where this is preferred.

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