erase_region

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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. It states that the operation erases to transparency, which implies a destructive modification of the layer's pixel data, but it does not specify whether the erasure is permanent, whether it affects only the selected frame and layer, whether it respects layer opacity or blend mode, or whether it can be undone. The 7 required parameters suggest a complex operation that could alter the sprite in non-obvious ways, and the description does not address these risks.

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 a single, short sentence that is immediately front-loaded with the verb 'Erase', making it easy to scan. There is no wasted wording. However, it is arguably too brief for a tool with 7 parameters and no annotations, but as a concise statement it earns a 4 for efficiency.

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 the tool's moderate complexity (7 params, all required, no output schema, no annotations), the description is incomplete. It does not explain the coordinate system, the effect on animation frames, whether the erasure is destructive to the sprite file, or any side effects on other layers. While sibling tools like move_region and copy_region may have similar descriptions, the description does not provide enough context for an agent to safely use this tool without making assumptions. The lack of any parameter descriptions and the absence of behavior details makes this a significant gap.

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?

The input schema has 0% description coverage, meaning no parameter descriptions are provided. The description only mentions 'rectangular region', which vaguely maps to the x, y, width, height parameters but does not explain units, coordinate origin, or how it relates to the layer's coordinate space. It also does not clarify the role of filename, layer_name, and frame_index, which are critical for targeting the correct sprite, layer, and frame. With zero schema descriptions, the description fails to compensate for the complete lack of parameter documentation.

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 clear action ('Erase') and a specific resource ('rectangular region'), and specifies the result ('to transparency'), which distinguishes it from sibling erase_color (color-based erasure) and delete_frame (frame deletion). However, it does not explicitly mention the target layer or frame, which are implied by the parameters but not stated.

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 does not provide any guidance on when to use this tool versus alternatives like erase_color, delete_frame, or clear_cel. It does not mention prerequisites (e.g., that the target layer must exist), nor does it warn about any limitations. The agent is left to infer from the name and parameters.

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