Prepare PCB Component Transform

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that, explaining why: nothing is written until an exact confirmation phrase is supplied. It adds real context beyond the annotations by describing what the preview returns (scope, expected coordinates) and that a confirmation phrase is required, though it doesn't say what happens if the expected target/coordinates no longer match.

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?

Two short sentences with the action set front-loaded and the safety caveat second; nothing is redundant. The mid-sentence list of preview contents is slightly dense but each item is informative.

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?

With 11 parameters, a nested target object, and no output schema, the description does well to describe the preview payload, but it leaves the target object (project/page/fingerprint) and timeoutMs unexplained and doesn't describe the failure mode when the live board doesn't match the expected target. Adequate but with clear gaps for a mutation-adjacent tool.

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 91%, so the schema already documents absolute x/y versus relative dx/dy, rotation versus dRotation, layer for flip, and the component designator format. The description only alludes to "expected coordinates" and adds no meaning beyond the schema, which is the expected baseline here.

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 and resource: prepares a PCB component transformation with the four concrete actions (move, rotate, flip, delete) enumerated. It is clearly distinct from siblings like easyeda_navigate_component or easyeda_prepare_pcb_layout by the resource it operates on, though it never names an alternative explicitly.

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?

"Does not modify the PCB until confirmed" implies the two-phase prepare-then-confirm workflow, but the tool never names the confirming sibling (easyeda_confirmed_action) or says when to use this instead of easyeda_navigate_component or easyeda_find_component for locating a part. Usage is implied rather than stated.

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