pcb_add_barcode

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

The annotations include destructiveHint=true, but the description does not explain what destructive side effects may occur, such as overwriting an existing marker or modifying the board file. It adds no behavioral context beyond the annotation, and the word 'Add' does not clarify the destructive aspect.

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 sentence with no superfluous words, making it very concise. However, it is so brief that it omits necessary information, though conciseness itself is strong.

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 6-parameter tool with a destructive hint, the description is severely under-specified. It omits barcode format choices, coordinate system, layer semantics, and any side effects. The presence of an output schema covers return values only, not the missing input and behavioral details.

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 has 0% description coverage and the description provides no parameter details. Property names like content, x_mm, y_mm, and barcode_type are self-evident, but the description does not explain value formats, units, coordinate system, or allowed barcode types, which is a significant 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 uses a specific verb ('Add') and resource ('production barcode marker') with a target location ('board file'), clearly stating the operation. It distinguishes from related tools like pcb_add_text, though it does not explicitly mention alternatives or scope.

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 is provided on when to use this tool versus alternative marker-adding tools (e.g., pcb_add_text, pcb_add_fiducial_marks), and no prerequisites or exclusions are mentioned. Usage is only implied by the tool name and brief description.

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