uv.average_islands_scale

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

The description states it averages scale but does not disclose behavioral traits such as whether it modifies UV islands permanently, what scope (active object only), or any side effects like distortion. No annotations are provided to compensate.

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 a single short sentence, which is concise and front-loaded. It efficiently conveys the core action, though it could be slightly more informative without losing brevity.

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 lack of output schema and minimal parameter info, the description is incomplete. It does not explain what 'average' means (e.g., uniform scaling based on selection), nor does it address multi-object scenarios or return values. Essential context is missing.

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 description coverage and only 1 parameter ('object'), the description fails to explain this parameter's meaning (e.g., default is active mesh object, optional). The schema itself has no descriptions, so the description should compensate but does not.

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 uses a specific verb ('average') and resource ('texel density / scale of all UV islands'), clearly stating what the tool does. It distinguishes itself from siblings like uv.pack_islands or uv.unwrap, which have different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., uv.pack_islands for packing, uv.smart_unwrap for unwrapping). There is no mention of prerequisites, limitations, or exclusions.

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