erase_color

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

No annotations are provided, so the description carries the full burden. It discloses that only opaque pixels are affected and that matching is per-channel with tolerance, which is useful. However, it does not state the nature of the mutation (e.g., whether pixels become transparent), irreversibility, or scope (layer/frame), leaving significant behavioral ambiguity 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?

One short, front-loaded sentence with no filler. Every word earns its place; it is appropriately sized for the information it conveys.

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 mutation tool with no annotations, no output schema, and four required parameters, this description is too thin. It lacks usage context, side effects, and parameter details beyond color/tolerance. An agent would have to infer or experiment to understand the operation's full effect.

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 is the only source of parameter meaning. It clarifies that 'tolerance' is applied per channel and that matching considers opacity, adding value beyond the raw schema. However, it does not explain the other parameters (filename, layer_name, frame_index) or the color format, leaving gaps for a tool with five 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?

The description states a specific verb ('erase'), resource ('opaque pixels matching a color'), and a defining qualifier ('within channel tolerance'). This clearly distinguishes it from geometric erasers like erase_region or clear_cel, making the tool's purpose immediately understandable.

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 given about when to use this tool versus alternatives such as erase_region, clear_cel, or replace_color. The description implies usage through its purpose but provides no explicit context, exclusions, or prerequisites.

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