copy_region

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the high-level operation and does not say whether the source is left untouched, whether the destination area is overwritten or composited, how out-of-bounds coordinates behave, or what the function returns.

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 concise and front-loaded in a single sentence. However, it is under-specified for an 11-parameter operation, so the brevity comes at the cost of useful structure and clarity.

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 tool with 11 parameters, 9 required, no annotations, and no output schema, this description leaves almost every decision to the agent. It does not clarify coordinate frames, defaults, mutation semantics, or return behavior, making it insufficient for correct invocation.

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 needed to explain the roles of the 11 parameters. It only hints at a rectangular region and a layer/frame destination, without mapping x/y/width/height to source geometry, dest_x/dest_y to placement, or describing the defaults of target_layer_name and target_frame_index.

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 ('Copy') and resource ('a rectangular region') plus a destination ('layer and frame destination'). It is not a tautology and broadly distinguishes the tool from siblings like move_region (copy vs move) and copy_sprite/copy_cel (region vs whole asset), though it does not name any alternative.

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 guidance on when to use copy_region instead of related tools such as move_region, erase_region, copy_cel, copy_frame, or draw_rectangle_at. The description implies a copy use case but provides no conditions, exclusions, or alternatives.

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