Ase Flatten Layers

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

With no annotations, the description carries the full burden. It does disclose the core destructive outcome: all layers are merged into one, which implies loss of individual layers. It does not mention irreversibility, hidden-layer behavior, or whether the change affects the saved file, but the essential behavior is stated.

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, front-loaded sentence with zero filler. It packs the operation and scope into five words and 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 simple and an output schema exists, so return-value details need not be described. Still, the definition lacks any parameter elaboration or usage context, making it only minimally complete for an agent that must invoke 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 0%, and the description does not mention sprite_path at all. The only parameter is self-explanatory by name, but the description adds no guidance about how the path is used or what kind of sprite resource is expected.

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 and resource: flatten all layers in the sprite into one. This clearly distinguishes it from siblings like ase_merge_layer_down or ase_export_layers, which have different semantics.

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 intended use is implied: use this when you want to reduce the entire sprite to a single composite layer. However, it does not explicitly state when to choose this over ase_merge_layer_down or krita_flatten, nor does it mention any caveats such as hidden layers being affected.

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