Ase Export Layers

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It mentions that out_dir defaults to output/layers_<sprite name>/, which is useful, and that include_hidden exports hidden layers. However, it does not clarify whether the tool creates the output directory, whether it overwrites existing files, what naming conflicts arise, or whether it works for all sprite formats. The reference to --split-layers suggests a CLI wrapper but does not explain the tool's behavior on failure or edge cases.

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 concise, two sentences, and front-loads the core function. It efficiently mentions the key behavioral details: the --split-layers flag, the default output directory, and the include_hidden option. There is no redundancy or filler, but it could be slightly more structured by separating the default directory from the flag explanation.

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?

Given the tool has an output schema (which likely describes the output paths or status), the description need not detail the return format. However, it lacks information on prerequisites (e.g., does the sprite need to be open?), edge cases (e.g., no visible layers, hidden layer behavior), and potential side effects (e.g., directory creation). For a tool with only 3 parameters, the description covers the essentials but leaves some gaps in operational context.

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 compensate. It explains out_dir's default behavior (output/layers_<sprite name>/) and include_hidden's effect (also exports hidden layers), which adds meaning beyond the schema. However, sprite_path is barely elaborated, only implied as the input sprite file. Given the description covers two of three parameters, it partially compensates for the low schema coverage, but not fully.

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 the tool exports each visible layer as a PNG named after the layer, which is distinct from ase_export_sprite (exports whole sprite) and ase_export_spritesheet (exports a spritesheet). It also mentions the flag --split-layers, which differentiates it from exporting a single image. The verb 'export' and resource 'layers' are specific, and the description conveys the exact output format.

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 for exporting layers individually, but it does not explicitly say when to use this tool versus ase_export_sprite or ase_export_spritesheet. It mentions include_hidden to also export hidden layers, giving a hint about typical use cases (visible layers only by default), but lacks explicit exclusions or comparisons. Given the large sibling list, more guidance on when to prefer this over other export tools would be valuable.

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