Navigate browser page

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the description needn't repeat those. It adds the crucial nuance about not changing the global active page, which is beyond the schema/annotations. No contradiction.

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 sentences, front-loaded with action, no fluff. Adds value without redundancy.

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 annotations and schema, description covers the key behavior and the global active page nuance. Lacks mention of timeoutMs, but that's in schema. Sufficient for a simple navigation tool.

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 coverage is 0%, so description should compensate. It mentions absolute HTTP(S) URL and the sessionId/pageId pair, but doesn't clarify timeoutMs or beyond what schema says. Partial coverage.

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 action: 'Navigate an explicitly addressed page to an absolute HTTP(S) URL.' It identifies the specific resource (page) and action (navigate), and distinguishes from siblings like browser_reload or browser_back by emphasizing the explicit address and URL.

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 description explicitly instructs to use the sessionId/pageId pair and clarifies that navigation never changes the global active page, which guides selection. It doesn't explicitly list alternatives (e.g., browser_get_url) but the context implies when to use this vs siblings.

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