browser_navigateDirect the current browser tab, or open a new one, to a specified URL. Use it to load pages and start browsing without a browser driver.
Navigate the current browser tab (or a new tab) to the given URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to navigate to | |
| newTab | No | Open the URL in a new tab (default: current tab) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral burden. It does not say whether navigation waits for page load, what happens on failure, or that navigating away from the current page may lose unsaved state, which are meaningful traits for a navigation tool.
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?
A single, front-loaded sentence with no filler; the primary action and target are stated immediately. It is efficient, though verging on under-specified rather than optimally structured.
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 simple two-parameter tool with a fully documented schema and no output schema, the description is minimally adequate. It omits behavioral details such as navigation timing or failure handling that would complete the picture.
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 100%, so both url and newTab are already documented in the schema, establishing a baseline of 3. The description's '(or a new tab)' merely restates the newTab parameter without adding format or default guidance beyond the schema.
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?
States a specific verb (Navigate) and resource (browser tab / URL), making the action immediately clear. It does not explicitly distinguish itself from siblings like browser_switch_tab or browser_list_tabs, but the URL-navigation purpose 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 description gives no when-to-use versus when-not guidance and names no alternatives. The parenthetical '(or a new tab)' hints that the newTab parameter exists but offers no condition for choosing tab behavior, leaving routing entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.