reorder_layer

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

No annotations are provided, so the description carries the full burden. It explains the 1-based position semantics but does not disclose whether the operation modifies the file in-place, requires the file to be open, or has side effects. This is adequate but not comprehensive.

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 compact, with a clear opening sentence followed by a structured argument list. Every sentence adds value, and the key positional information is front-loaded. No wasted words.

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 modification tool with three parameters, the description covers the core semantics (especially position). However, it lacks details on return values, error cases, or confirmation that the file is modified. Given the simplicity, it is mostly complete.

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?

The input schema has no descriptions (0% coverage), but the description adds meaningful context: filename is 'Aseprite file to modify', layer_name is 'Layer to move', and position is 'Target stack position, 1-based where 1 is the bottom layer'. This significantly clarifies the parameters beyond their names.

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 clearly states 'Move a layer to a new position in the layer stack,' using a specific verb and resource. It distinguishes itself from sibling tools like add_layer, delete_layer, and rename_layer by focusing on reordering.

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 usage (reordering layers) but provides no explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, though no sibling tool duplicates this functionality.

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