reorderLayer

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

With no annotations, the description carries the full behavioral burden, yet it only says the layer moves vertically. It omits whether a composition must be specified, how the layer is identified (name vs. index), what happens when the target does not exist, and whether keyframes or parenting are affected.

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 tightly written sentence with the core behavior front-loaded and the operation list provided as a compact parenthetical. There is no filler or repetition.

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 seven-parameter mutation tool with no annotations and no output schema, the description leaves key operational details unresolved. The schema is rich, but the agent still lacks guidance on parameter combinations and side effects that are essential for calling it correctly.

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 100%, so the parameters are already documented, including the operation enum and 1-based newIndex. The description repeats the operation enum but adds no new detail about choosing between layerName/layerIndex or targetLayerName/targetLayerIndex.

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?

States a specific verb and resource ('Reorder a layer vertically in the layer stack') and enumerates the five supported operations. It is clear what the tool does, though it does not explicitly distinguish itself from nearby siblings such as reorderEffect or setLayerProperties.

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 gives no when-to-use or when-not-to-use guidance and names no alternatives. An agent must infer which of the five operations or target-reference parameters to choose without any stated conditions.

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