Import PCB Changes

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

No annotations are provided, so the description must fully disclose behavior. It only says 'Synchronize' with no mention of side effects, destructive actions (e.g., overwriting PCB edits), required access, or what changes occur. This is a significant transparency gap for a tool that likely modifies the PCB file.

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 very concise, with one functional sentence and a pointer to a relevant instructions file. It is front-loaded with the main purpose and does not waste words. The instruction file reference could be seen as extra, but it is useful and does not bloat the description.

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 synchronization tool that likely needs to handle conflicts, file paths, and schematic-PCB relationships, the description provides almost no context. With no output schema and no annotations, the agent has no idea what success looks like, what errors can occur, or what the instruction file contains. It is far from complete.

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 input schema already provides 100% coverage with descriptions for both parameters ('Target .kicad_pcb path' and 'Optional root .kicad_sch override'). The description does not add additional meaning about how these parameters interact or what values are expected, so it does not exceed the schema baseline.

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 uses the specific verb 'Synchronize' with a clear resource ('one KiCad PCB from its associated schematic'), which conveys the tool's core function. It does not explicitly name sibling tools but the callback to 'associated schematic' differentiates it from other PCB layout tools. However, the term 'Synchronize' could be interpreted more clearly, and the instruction file reference is not part of the purpose.

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 gives no guidance on when to use this tool versus alternatives like make_pcb_layout or auto_route_pcb. The reference to an instruction file implies there are detailed usage rules, but the description itself does not state prerequisites, typical scenarios, or alternatives. This leaves the agent to infer usage context.

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