pcb_batch_move

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

With no annotations provided, the description must fully disclose behavior, but it only states a batch move operation. It does not mention coordinate semantics, behavior on missing designators, partial failure handling, or whether the operation persists immediately. This is a significant transparency gap for a mutating tool.

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, clear, front-loaded phrase with no unnecessary words. However, it is so terse that it under-specifies some behavioral aspects, though those are covered by the schema. It is concise but not fully complete.

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 batch operation with nested parameters and no output schema or annotations, the description should provide more context about execution semantics, return behavior, or failure handling. It only defines the action, leaving critical operational details undocumented.

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% coverage for the single 'moves' parameter with its description listing structure [{designator, x, y, rotation?}]. The tool description adds no additional parameter meaning, so the baseline of 3 applies.

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 '批量移动多个元件' (Batch move multiple components) uses a specific verb 'move' and resource 'components' with explicit batching scope. This clearly differentiates it from sibling tools like pcb_move_component (single component move) and pcb_relocate_component.

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 batching intent is implied by the word '批量' and the plural '多个', but there is no explicit when-to-use or when-not-to-use guidance. Alternatives such as pcb_move_component for single moves are not mentioned, leaving the usage context only implied.

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