kicad.move_component

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

No annotations provided, so description carries full burden. Fails to disclose critical CAD-specific behavior: coordinate units (mm/mils), absolute vs. relative positioning, whether connected traces/wires move with the component or become disconnected, and whether the operation is undoable.

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?

Single sentence is efficient but underspecified for the domain. While not verbose, it lacks 'front-loaded' critical information (units, coordinate context) that should take priority over brevity given the CAD context.

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 PCB/schematic CAD mutation tool with no annotations and undocumented parameters, the description is inadequate. Despite having an output schema (not shown), the description omits coordinate system context, units, and error handling (e.g., invalid reference designators), which are essential 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 has 0% description coverage (only titles 'Ref', 'X', 'Y'). Description fails to compensate by not explaining that 'ref' is a reference designator (e.g., 'R1'), or what coordinate system/units X/Y use. Complete parameter documentation gap.

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 action ('Move') and target ('component') with scope ('to a new position'). It implicitly distinguishes from kicad.add_component (creation vs. repositioning), though it doesn't explicitly clarify PCB vs. schematic context or coordinate system details.

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 versus alternatives like kicad.place_via or kicad.route_trace. Does not mention prerequisites such as the component needing to exist beforehand (via kicad.add_component) or requiring an open project.

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