erase_pixels

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

With no annotations, the description must carry the load, and it does disclose two meaningful traits: the exact effect (transparent #00000000) and atomicity ("a single undo transaction"). It omits other relevant behavior such as layer-resolution rules, error handling, and whether partial erasures are possible.

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 zero filler; the verb, mechanism, and atomicity are all packed economically into one line.

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 5-parameter mutation tool with no annotations and no output schema, the description covers the core effect and undo semantics but leaves gaps around return values, layer targeting, and failure modes. Adequate but not 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 100%, so layerName/layerIndex/frameNumber/returnPreview are already documented. The description adds no additional parameter meaning (e.g., precedence between layerName and layerIndex), so baseline 3 is appropriate.

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 verb ("Erases") and resource ("a list of pixel coordinates") plus the exact mechanism ("turning them transparent (#00000000)"). This implicitly distinguishes it from set_pixels/set_pixel, though it never names a sibling.

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?

There is no explicit guidance on when to choose this tool over set_pixels, replace_color, or the drawing primitives. Usage is only implied by the word "erase," with no conditions or exclusions stated.

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