Ase Delete 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 only says 'Delete a layer by name,' which implies a destructive operation but doesn't disclose irreversibility, effect on cels, or error handling. This is insufficient for a destructive tool.

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, direct sentence, which is concise and front-loaded. It wastes no words, but it is under-specified, lacking any behavioral or usage detail. Still, it is efficiently sized for a simple action.

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 delete operation with two parameters, the description is minimal but lacks critical context: no mention of permanence, undo support, or what happens if the layer doesn't exist. Given no annotations, the description should provide more safety-relevant information.

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 coverage is 0% and the description doesn't explain the parameters. Although the names sprite_path and layer_name are self-explanatory, the description doesn't add meaning beyond the schema, nor does it clarify formats or constraints.

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 clear verb and resource: 'Delete a layer by name.' It distinguishes from other delete operations (e.g., ase_delete_frame) by specifying 'layer'. However, it doesn't mention the sprite context, which is implied by the sprite_path parameter, so it's not a 5.

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?

No guidance on when to use this tool versus alternatives like ase_merge_layer_down or ase_set_layer_visibility. It doesn't state prerequisites (e.g., sprite must be open) or consequences, leaving the agent without direction on when to choose this over similar layer operations.

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