uv.layer_set_active

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

Description only states it sets the active layer. No annotations are provided, so the description carries the burden. It does not disclose behavior on invalid name, side effects, or required mode (e.g., Edit Mode).

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?

Single sentence that clearly states the action and method. No extraneous words, front-loaded.

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 simple setter with two parameters, the description is too terse. It omits error conditions, return value, and context requirements. Given no annotations or output schema, more detail is needed.

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%, but the description adds minimal value: 'by name' hints at the 'name' parameter. The 'object' parameter is only described by its schema title. Description does not compensate for lack of schema descriptions.

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 'Set the active UV layer by name' is a clear verb+resource. It distinguishes from sibling tools like uv.layer_create or uv.layer_delete by specifying 'set active'.

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 on when to use this tool versus alternatives like uv.layers, uv.layer_create, or uv.layer_delete. No prerequisites or context requirements mentioned.

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