uv_unwrap

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

No annotations provided, so description must disclose all behavioral traits. It lacks information on side effects (e.g., overwriting UVs), permission needs, or whether it modifies the object. Only mentions prerequisite seams.

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?

Five sentences covering action, prerequisite, parameters, and return value. Mostly efficient but includes redundant 'Args' section that mirrors schema.

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?

Describes return as confirmation dict and notes seam requirement. Lacks prerequisite that object must be a mesh, or that it should be selected. Adequate but not fully comprehensive given output schema exists.

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?

With 0% schema coverage, description adds basic meaning: object_name is mesh name, method specifies two options. However, it does not explain differences between methods or default value behavior, which is minimal compensation for missing schema details.

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?

Clearly states the tool unwraps a mesh object's UVs using standard unwrap. Distinguishes from sibling 'smart_uv_project' by specifying 'standard unwrap' method.

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?

Mentions requirement of seams for best results, implying use of 'mark_seam' before this tool. No explicit when-not or alternative methods like 'smart_uv_project'.

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