Navigate a browser session to a URL, opening the page so AI agents can continue with further browser steps in that isolated session.
Navigate to a URL
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to navigate to | |
| session | No | Session id (default "default"). Each session is an isolated browser (own cookies, tabs) that runs in parallel with the others. Created on first use. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare openWorldHint=true, destructiveHint=true, and readOnlyHint=false, so the risky, outward-facing nature is covered structurally. The description adds nothing — it doesn't say whether navigating replaces current page state, whether it blocks until load completes, or that it may discard unsaved form content.
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?
Three words, front-loaded and waste-free, but the brevity comes at the cost of under-specification rather than disciplined editing. It is not verbose; it is simply thin.
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?
The one required parameter is well documented in the schema and the safety profile is in annotations, so an agent can technically call it. However, for a destructive, open-world navigation tool with 29 siblings and no output schema, the description omits what actually happens on invocation (load waiting, state replacement, error behavior).
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%, with both url and session fully documented inline (including session isolation semantics). The description contributes no additional parameter meaning, which is acceptable at baseline 3 given the schema does the work.
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 "Navigate to a URL" is a verbatim restatement of the tool's title and a near-restatement of its name (browser_navigate). It conveys the verb+resource but adds nothing an agent couldn't infer from the identifier, and it does not distinguish this from browser_navigate_back or browser_tabs.
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?
There is no guidance on when to use this versus alternatives such as browser_navigate_back, browser_tabs, or opening a session first. Usage is only implied by the name itself; no preconditions or exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.