pcb_navigate_to_region

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds coordinate-frame behavior but says nothing about side effects on the viewport, whether a document must be open, or what happens on auto-switch — a modest addition over the annotations.

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?

Front-loaded with the purpose, then coordinate semantics, then related tools — a logical order. The sentence about widths/diameters being in mil is filler for a tool with no length parameters, a small waste of space.

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 no output schema, the description need not explain return values, and it adequately covers the coordinate system and companion tools. It could go further on instance/document auto-switch behavior, but the schema handles those parameters.

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 coverage is 100%, but the schema descriptions are minimal (e.g. 'Top boundary Y'). The description compensates by specifying units (mil), the canvas coordinate frame relative to origin, and axis directions (+X rightward, +Y upward), which materially aids correct invocation.

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 pair (navigate and zoom) and resource (PCB editor viewport) with a clear scope (fit a specific region). This implicitly distinguishes it from pcb_zoom_to_board, but it never names the siblings it is not, so an agent must infer the difference.

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 routes the agent to related tools for coordinate work (pcb_canvas_origin, pcb_convert_coordinates), which is helpful context. However, it gives no explicit when-to-use-this-vs-pcb_zoom_to_board or pcb_navigate_to guidance, leaving the selection to inference.

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