Ase Render Onion Skin

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It explains the processing pipeline: flattened frames exported via CLI, composited with Pillow over white, nearest-neighbor scaled, and returning a PNG path. It does not cover file-creation side effects or failure modes, but the disclosed rendering behavior is substantive and clear.

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 three tightly written sentences with no filler. It front-loads the core behavior, then adds implementation detail, and ends with the return value. Every sentence contributes useful information.

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 provides a coherent end-to-end mental model, and the output schema covers the return value, so explaining the PNG path is a bonus. However, for seven parameters with 0% schema description coverage and no annotations, the missing per-parameter semantics and absent sibling-routing guidance leave meaningful gaps. It is adequate at a high level but not fully complete.

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 needed to compensate for seven parameters. It only hints at concepts—neighboring frames (before/after), ghosts (ghost_opacity), scaling (scale), and PNG path (output_path)—without defining any parameter's meaning, valid range, or interaction. An agent cannot reliably determine how to set before/after or ghost_opacity from the description alone.

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 ('Render'), names the exact resource (a frame plus translucent ghosts of neighboring frames), and states the purpose (checking motion continuity). It also differentiates itself by noting it works 'without opening Aseprite,' making it distinguishable from export and single-frame preview siblings.

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 stated purpose gives a clear intended context—checking motion continuity—and 'batch onion-skinning' implies a preview workflow. However, it does not name alternatives or state when not to use this tool versus siblings like ase_view_frame or ase_compare_frames, so usage guidance is only implied rather than explicit.

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