pcb_place_dimension

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

With no annotations provided, the description must carry the behavioral disclosure burden. It adds coordinate units in mils, the default layer, auto-orientation behavior, and that it returns a confirmation dictionary, but it does not state that the tool mutates the PCB by creating an object or requires an active document.

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 front-loaded with the core action, then briefly explains orientation behavior, followed by compact Args and Returns sections. Every sentence supports invocation or understanding of the parameters.

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?

It covers purpose, orientation logic, all parameters, and a return confirmation, which is sufficient to invoke the tool. It omits the active-document prerequisite and mutation side effects, which are notable for a placement tool with no annotations.

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%, so the description must compensate for all six parameters. It does so by documenting x1/y1 and x2/y2 as reference points in mils, layer with its default, and orientation with allowed values and auto behavior when empty.

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 states a specific verb, 'Place', and resource, 'linear dimension between two points'. The word 'linear' clearly distinguishes it from sibling tools pcb_place_angular_dimension and pcb_place_radial_dimension.

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?

It explains horizontal versus vertical measurement and auto-detection, which gives useful context for the orientation parameter. However, it does not explicitly say when to choose this tool over angular or radial dimension siblings, nor does it state prerequisites such as requiring an active board.

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