aseprite_apply_palette

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

No annotations are provided, so the description carries the full disclosure burden, yet it only implies mutation. It never says whether colors are remapped/quantized in place, whether the source file is overwritten or a new file written, or what the result looks like.

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?

A single front-loaded sentence with no filler; the action and target come first. It is efficient, though arguably too terse given the tool's mutation semantics.

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 file-mutating tool with no annotations and no output schema, the description omits critical operational detail: in-place vs new-file behavior, palette conflict handling, and any overwrite risk. Not sufficient for an agent to invoke it safely beyond the happy path.

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 already 100%, and the description merely repeats the preset examples ('pico-8', 'endesga-32', 'gameboy') that the schema already lists. It adds no meaning about customPalette format, precedence, or interaction between the two palette parameters.

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?

States a specific verb ('Apply') and resource ('a color palette preset ... to a sprite'), and the example presets make the operation concrete. It is distinguishable from siblings like aseprite_draw_pixels or aseprite_convert, though it never explicitly contrasts with them.

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 rather than alternatives (e.g. aseprite_convert or aseprite_draw_pixels), and no exclusions or prerequisites. Nothing tells the agent whether palettePreset and customPalette are mutually exclusive.

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