navigate_page

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

Annotations only indicate readOnlyHint=false, so the description carries the burden of explaining side effects. It confirms the navigation action but does not disclose page state changes, beforeunload handling, or other behavioral consequences beyond what the schema already lists.

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 compact sentence with the primary action front-loaded and no filler. Every phrase earns its place, and the fallback behavior is stated efficiently.

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 7-parameter tool with no output schema and sparse annotations, the description plus schema is minimally workable. It misses guidance on mode-specific parameter applicability and page targeting context, making it adequate for simple navigation but incomplete for more nuanced use.

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 100%, so the baseline is 3. The description adds one useful semantic—omitting a URL falls back to the project URL—which is not in the schema, but it does not elaborate on the other six parameters.

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 and resource: navigate by URL, back, forward, or reload. It clearly communicates the core action and differentiates from the name alone, though it does not explicitly contrast with siblings like new_page or select_page.

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?

The only guidance is 'Use project URL if not specified otherwise,' which addresses a default parameter value rather than when to choose this tool over alternatives. No sibling tools or exclusions are mentioned, leaving tool-selection decisions to inference.

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