Ase Add Frames

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 states the key mutation side effect with 'Saves in place' and adds operational context with 'headless CLI.' It also discloses the optional tag-wrapping behavior, giving an agent a solid picture of what happens when the tool is invoked.

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 only three sentences, all of which add value. The core operation is front-loaded, the use case is concise, and the in-place save/headless behavior is stated in a short final sentence. There is no redundant repetition of schema fields or annotations.

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 description gives enough high-level context for an agent to understand the operation and the fact that the file is modified in place, and the presence of an output schema means return values need not be described. Still, there are gaps around layer semantics, image ordering, and what happens when a tag_name is or is not supplied, which leaves some ambiguity for a fully autonomous agent.

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, and it does provide conceptual mappings: PNGs correspond to image_paths, the .aseprite sprite corresponds to sprite_path, 'new layer' maps to layer_name, and 'animation tag' maps to tag_name. However, it does not explain ordering, path formats, defaults, or the exact effect of layer_name when a layer already exists, so compensation is incomplete.

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 opens with a specific verb and resource: 'Append each PNG as a new animation frame on a new layer of an .aseprite sprite.' It clearly distinguishes itself from sibling frame tools by focusing on PNG inputs and optional tag wrapping, so an agent can tell it apart from tools like ase_add_frame or ase_add_frames_blank.

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?

It explicitly provides a use case: 'Useful to turn RD generations into idle-animation frames.' This gives clear context for when the tool is appropriate, though it does not explicitly contrast it with sibling alternatives such as ase_add_frames_blank or ase_import_layer.

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