Ase Reorder Layer

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

With no annotations, the description carries the full burden of disclosing behavior. It only states the action (move) and the position convention, but does not mention side effects such as modifying the sprite file, whether it is reversible, or how it interacts with other layers. This is minimal beyond the purpose statement.

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 sentence with no filler. It front-loads the action and includes the essential clarification about 1-based indexing. Every word earns its place.

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 is a simple reorder operation, and an output schema exists though its content is not visible here. The description is adequate for the action itself, but missing parameter explanations and behavioral context (e.g., persistence, errors) make it only minimally complete for an agent.

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%, so the description must explain parameters. It only clarifies 'position' (1-based), but leaves sprite_path and layer_name undefined. While these may be inferable from sibling tools, the description itself does not provide their semantics.

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 states a specific verb ('Move'), a resource ('layer'), and a precise meaning of position ('1-based stack position (1 = bottom)'). This clearly distinguishes it from other layer operations like add, delete, rename, or merge, all of which appear as siblings.

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 implies the tool is for reordering layers but gives no explicit when-to-use or when-not-to-use guidance, nor names alternatives. It relies on the verb 'reorder' and the sibling context, which is implied usage rather than explicit direction.

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