Navigate to EasyEDA Pro region

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

Annotations already indicate readOnlyHint=true. Description adds minimal behavioral context beyond that, such as not discussing viewport changes, zoom behavior, or whether it affects the active document state.

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?

Single efficient sentence with no wasted words. However, being overly concise sacrifices necessary detail for parameter understanding.

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?

Given the 7 parameters and no output schema, the description is too brief. Missing details like coordinate units, relationship between param groups, timeout purpose, and expected behavior.

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?

With 0% schema description coverage, the description only hints at parameters via 'coordinates or a rectangular region', suggesting x,y or top/left/right/bottom, but does not explain timeoutMs or parameter combinations. Incomplete semantics for a 7-parameter tool.

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?

Description clearly states the tool navigates to coordinates or a rectangular region in EasyEDA Pro PCB/document. This differentiates it from siblings like easyeda_navigate_component (which targets components) and easyeda_zoom_board (zoom control).

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for navigation but does not mention exclusions or contrast with sibling tools like easyeda_navigate_component.

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