Browser MCP Server

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

No annotations are provided, so the description carries full burden. It states the basic action but doesn't disclose important behavioral traits: whether navigation blocks until completion, what happens on invalid URLs, whether it follows redirects, authentication requirements, or what constitutes success/failure. The reference to browser_docs hints at more information elsewhere but doesn't provide it directly.

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 extremely concise - a single sentence that directly states the tool's purpose. It's front-loaded with the core action and includes a helpful reference to related documentation. There's zero wasted verbiage or unnecessary elaboration.

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 navigation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after navigation (does it wait for page load?), what the return value might be, error conditions, or how this interacts with the browser state. The reference to browser_docs acknowledges missing information but doesn't provide it within the description itself.

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 the single 'url' parameter fully documented in the schema. The description doesn't add any parameter semantics beyond what the schema already provides (URL to navigate to). With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 to a URL') and resource ('in the browser'), making the purpose immediately understandable. It distinguishes from siblings like browser_click or browser_type by specifying navigation rather than interaction or input. However, it doesn't fully differentiate from browser_reload or browser_go_back/forward which also change page location.

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 provides no guidance on when to use this tool versus alternatives. It mentions 'see browser_docs' which suggests documentation exists elsewhere, but within the description itself there's no indication of prerequisites, when navigation is appropriate versus other page-loading tools, or any constraints on usage.

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