reorder-layer

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

With no annotations, the description must disclose side effects, but it only restates the basic mutation ('Change... stacking order') and a parameter constraint. It does not address reversibility, required selection defaults, or effects on other layers.

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?

Two short sentences front-load the core purpose and immediately give the key usage rule. There is no filler or repetition of schema text.

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?

The tool has 9 optional-looking parameters and cross-parameter constraints, but the description never mentions how to identify the layer being moved (layerName/layerIndex) or whether active selection is used as a default. The complete invocation contract is therefore not documented.

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 coverage is 100%, so the baseline is 3. The description adds value by imposing a mutual-exclusion constraint among toPosition, before*, and after* that the schema's standalone property descriptions do not convey. It remains slightly ambiguous about how the before/after name-index pairs combine.

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 opens with a specific verb and resource: 'Change a layer's stacking order (z-order) within its composition.' This clearly states the tool's function and distinguishes it from sibling operations like duplicate-layer, set-layer-parent, or precompose-layers.

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?

'Provide exactly one of toPosition, before*, or after*' gives an explicit usage constraint and names the three destination alternatives. It does not discuss explicit alternatives to this tool, but the stacking-order operation is unique among the siblings and the context is clear.

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