batch_move_footprints

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

With no annotations, the description carries the full burden. It usefully discloses that all moves occur in a single undo step, but omits permission requirements, error handling, and behavior for missing or locked footprints.

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 purpose is front-loaded in one sentence, followed by a compact Args block and a concrete example. Every part earns its place with no filler.

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 and a vague schema, the description covers the essential call shape and the undo grouping behavior. Remaining gaps are minor but real: it does not state whether x_mm/y_mm are absolute coordinates and does not describe failure handling for invalid references.

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% and the nested moves array has no property documentation. The description fully compensates by naming required keys 'reference', 'x_mm', 'y_mm', optional 'angle_deg', and providing a concrete example.

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?

States a specific verb (move/rotate), resource (footprints), and scope (several in one undo step). This clearly distinguishes it from sibling single-item tools like move_footprint and rotate_footprint.

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 implies batch use through 'several footprints in a single undo step,' but gives no explicit guidance on when to prefer this over individual move/rotate calls or arrangement tools like arrange_row. Usage is inferable but not spelled out.

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