Navigate View

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

The annotation indicates idempotency, which the description does not contradict. However, the description adds no extra behavioral context, such as whether this selects nodes, scrolls, or zooms. With annotations covering basic safety, the description provides minimal added value.

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, straightforward sentence with no unnecessary words. It is front-loaded with the action and target.

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 tool's simplicity (one required parameter, idempotent, with output schema), the description is mostly complete. It could briefly mention the effect on the viewport (e.g., pans/scrolls) to be fully self-contained.

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 input schema already provides 100% coverage for the 'ids' parameter with a clear description. The tool description does not add further meaning or usage details beyond what the schema states.

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 clearly states the tool navigates the editor view to pages or nodes, which is specific and distinguishes it from most sibling tools that focus on editing or information retrieval. However, it does not explicitly differentiate from potential alternative navigation methods.

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 alternatives. For example, there is no mention of whether to use this over selecting nodes directly or using other view control tools.

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