pcb_batch_move

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only restates the operation and does not clarify whether the move is absolute or relative, whether the operation overwrites existing positions, what happens on invalid designators, whether the action is reversible, or what the tool 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 a single efficient sentence with no filler, and the key batch/multiple scope is front-loaded. It is concise and well structured, though it sacrifices important contextual detail.

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 mutating tool with no annotations and no output schema, this one-phrase description is not enough for confident invocation. It omits coordinate units, behavior on partial failure, interaction with current selection, and any return value expectations.

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 schema already provides 100% description coverage for the single parameter, defining the moves array structure with required designator, x, y and optional rotation. The description adds no parameter-specific meaning, so the baseline score of 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 Chinese description '批量移动多个元件' names a specific action (batch move) and resource (multiple components). It distinguishes the tool from single-component move siblings like pcb_move_component by emphasizing 'batch' and 'multiple', though it leaves some ambiguity about whether '元件' means PCB footprints or generic design elements.

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 word '批量' (batch) and '多个' (multiple) imply this tool is for moving several components at once rather than a single component, which is the likely alternative pcb_move_component. However, there is no explicit when-to-use guidance, no exclusion of alternatives, and no mention of constraints like designator existence or selection prerequisites.

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