uv-cube_project

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

No annotations provided, and description does not mention side effects, prerequisites (like edit mode), or how it affects existing UVs (e.g., replaces or blends).

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?

One concise, clear sentence with no redundant words or jargon.

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?

Simple tool, but description omits prerequisites (e.g., faces must be selected in edit mode, mesh must be active) and consequences (overwrites existing UVs). Adequate for a basic operation but not fully explicit.

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 already provides clear titles for both params ('Mesh object to project' and 'Size of the projection cube'). Description adds no extra detail on how cube_size affects the projection or how object selection behaves beyond defaulting to active.

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 it cube-projects selected faces onto the UV map, distinguishing it from other UV projection methods like sphere or smart unwrap.

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?

Does not specify when to choose cube projection over alternatives (e.g., for box-like objects, or when spherical/planar would be better). Lacks any contextual guidance.

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