Navigate to EasyEDA Pro component

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

Annotations already declare a safe, read-only, non-destructive, non-open-world operation, so the bar is lower. The description does add one useful behavioral fact beyond them — that navigation only succeeds 'when the extension can locate it' — but it never says what failure looks like, whether the view is restored on failure, or why idempotentHint is false for a repeat-navigation action.

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?

One front-loaded sentence with no filler, and the action is stated before the caveat. It is efficient, though the extreme brevity is part of why other dimensions are thin rather than a virtue in itself.

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 simple two-parameter navigation tool with annotations covering safety, the description is close to complete about what it does. With no output schema, however, it should have said what a successful call returns or how a 'couldn't locate it' outcome is surfaced, and it leaves timeoutMs behavior completely unexplained.

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 only 50%: 'query' is documented in the schema but 'timeoutMs' has no description anywhere. The description mentions no parameter behavior at all, so it fails to compensate for the undocumented timeout or to clarify accepted query formats (designator vs free-text match).

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 names a specific verb pair (navigates/highlights), the resource (a component), and the environment (the EasyEDA Pro editor), so an agent can tell this is a viewport navigation action rather than a data query. It does not explicitly distinguish itself from near neighbors like easyeda_navigate_region, easyeda_highlight_net, or easyeda_find_component, which is the only thing keeping it from a 5.

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?

Usage is only implied: an agent can infer it should call this when it wants to move the view to a component rather than fetch its data. There is no explicit when-to-use, no mention of easyeda_find_component as the lookup alternative, and no statement of prerequisites such as having the document open.

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