erase_color

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

With no annotations, the description carries full responsibility. It fails to mention that the tool modifies the file destructively, that it sets alpha to 0, or any side effects (e.g., impact on other layers). The return behavior or confirmation is not described.

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 extremely concise: one sentence for purpose then a clean argument list. No wasted words, front-loaded with the core action.

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?

Given 5 parameters, no output schema, and no annotations, the description covers parameter semantics but lacks behavioral context (destructive nature, in-place modification, return value). It is minimally complete for usage but not fully comprehensive.

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 provides all parameter meanings. It explains filename, layer_name, frame_index (starting at 1), color (hex format with example), and tolerance (range 0-255, default 0). This is clear and sufficient, though it could clarify color format restrictions.

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 clearly states the tool's purpose: 'Make all pixels of a given color transparent (like a magic eraser).' It specifies the action (make transparent) and resource (pixels of a given color), distinguishing it from siblings like replace_color or erase_region.

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 description provides an analogy ('like a magic eraser') implying usage, but does not explicitly state when to use versus alternatives. No guidance on when not to use or prerequisites. Sibling tools with similar functions (e.g., replace_color) are not contrasted.

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