move_region

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

The description discloses that the old location is cleared, a key behavioral trait. With no annotations, the description carries the full burden. It does not mention side effects on layer/frame, undo history, or error handling, but the core mutating behavior is stated.

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 sentence of 9 words that directly conveys the core purpose. No superfluous content.

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 complexity (9 params, nested region object, no output schema), the description omits details like how to specify the region (rect/pixels/selection), error conditions, and return values. It is insufficiently complete for an AI agent to use reliably without additional context.

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 high (78%), so the schema already documents most parameters. The description adds no extra meaning to parameters beyond the schema. 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 clearly states the verb 'Move' and the resource 'region', specifying the operation of moving by (dx,dy) and clearing old location. It distinguishes from sibling tools like copy_region and cut_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?

No guidance on when to use this tool versus alternatives like shift_layer or copy_region. No prerequisites or exclusions mentioned. Usage is only implied.

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