navigate_page

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

Annotations only declare readOnlyHint=false, so the description carries the disclosure burden. It adds a default-URL fallback, but says nothing about the fact that navigation replaces the current page's document/state, how the timeout or initScript options behave in practice, or what happens on failed navigation. For a mutating navigation tool this is thin.

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?

Two short sentences with the core action front-loaded and the defaulting rule second. Nothing is padded or redundant.

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 navigation tool with no output schema and only a minimal readOnlyHint annotation, the description stops at listing modes and never touches the richer behaviors (initScript injection, cache bypass, beforeunload handling) that make this tool nontrivial. The schema fills those gaps, but the prose leaves the agent without any navigation-level framing.

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% across all 7 parameters, including the per-mode constraint on url and the handleBeforeUnload default, so the schema does the heavy lifting. The description adds no meaning beyond that, which is exactly the baseline-3 case.

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 concrete verb (navigate) and enumerates the four modes (url, back, forward, reload), matching the schema enum and clearly distinguishing it from siblings like new_page, close_page, and select_page. It stops short of naming an alternative tool, but the action set is unambiguous.

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 a default-value note: 'Use project URL if not specified otherwise.' There is no statement of when to prefer this over new_page or select_page, nor any prerequisite or precondition. Usage must be inferred from the tool name alone.

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