Ase Delete Slice

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without indicating that deletion is irreversible, what happens if the slice does not exist, whether the sprite must be saved, or any other side effects. This is a significant gap for a destructive operation.

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. Each word contributes meaning, and the action is front-loaded. It is appropriately concise for a simple delete operation, with no wasted text.

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?

Even though an output schema exists, the tool is destructive and requires context about prerequisites (e.g., knowing the slice name from ase_list_slices), error handling for missing slices, and the effect on the overall sprite. The description provides none of this, so an agent would need to infer critical operational details, making the definition incomplete for safe invocation.

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 two required string parameters with no descriptions (schema coverage 0%). The description only hints at the 'name' parameter via 'by name' but says nothing about 'sprite_path'—how it identifies the sprite file, its expected format, or its relationship to 'name'. The description adds minimal value beyond the raw schema.

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 action (delete), a specific resource (slice), and the selection mechanism (by name). This clearly distinguishes it from sibling tools like ase_create_slice, ase_set_slice_center, and ase_list_slices, which have different actions on the same resource.

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 is provided on when to use this tool versus alternatives, nor any prerequisites such as obtaining slice names via ase_list_slices. The description does not mention exclusions, conditions, or when deletion is appropriate, leaving the agent without decision support.

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