Browser Instrumentation MCP Server

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

With no annotations provided, the description carries full burden and does well by explaining the operation's nature ('inspect operation'), the automatic protocol handling ('https:// added if no protocol specified'), and what gets returned ('page title and final URL after navigation'). It doesn't mention potential side effects like page loading time or navigation failures.

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 perfectly structured with a clear purpose statement, brief explanation, and organized parameter/return sections. Every sentence earns its place, with no wasted words, and key information is front-loaded in the first sentence.

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 the tool's moderate complexity, no annotations, and the presence of an output schema (implied by the Returns section), the description is complete enough. It covers purpose, usage context, parameter semantics, and return values, providing everything needed for an agent to understand and invoke this tool correctly.

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?

With 0% schema description coverage, the description fully compensates by providing clear semantics for both parameters: 'session: Name of the browser session' and 'url: URL to navigate to (https:// added if no protocol specified)'. This adds essential meaning beyond the bare 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?

The description clearly states the verb ('Navigate') and resource ('to a URL') with specific purpose ('for observation'). It distinguishes from siblings by explaining this is an 'inspect operation' that 'sets up what you want to observe', differentiating it from action-oriented browser tools like browser_act_click.

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 clear context that this is an 'inspect operation' for 'observation' setup, which implicitly suggests when to use it versus action tools. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the many sibling tools.

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