compare_schematic_to_pcb

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

No annotations are provided, so the description must disclose behavioral traits on its own. It only lists what is compared but does not mention whether this is a read-only operation, what the output format is, whether it reports only mismatches or full data, or if any prior setup is needed. This is a significant gap for a comparison 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 focused sentence that gets straight to the point, using an active verb and specific comparison targets. There is no redundancy or filler; however, its brevity leaves out important usage and behavioral context, though that is more of a completeness concern.

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?

The tool is relatively complex (multi-file comparison with multiple comparison dimensions), and while an output schema exists, the description gives no context on prerequisites, return behavior, or how it fits into the overall design review workflow. With 2 required parameters and no explanation, the description feels incomplete for effective tool selection and 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 description coverage is 0% and the description does not elaborate on the two required path parameters. The names schematic_path and pcb_path are self-explanatory to a degree, but the description adds no detail about expected formats, file types, or relationships. It fails to compensate for the lack of schema descriptions.

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 tool compares specific attributes (RefDes, values, net names, pin/pad sets) between schematic and PCB. The verb 'Compare' is specific and distinguishes it from sibling comparison tools like compare_bom_to_design which focuses on BOM items rather than these electrical/net attributes.

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 implies the tool is used for comparing schematic and PCB on specific electrical attributes, but provides no explicit guidance on when to choose this over alternatives like validate_pin_pad_mapping or compare_bom_to_design. No exclusions or precondition details are given.

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