browser_navigate

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

Without annotations, the description reveals that by default no image tokens are consumed, the screenshot is discarded after OCR, and visual mode returns a PNG. This provides useful behavioral insight, though it omits potential side effects like cookie handling or timeout behavior.

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 two sentences, no wasted words. The first sentence states the core purpose, the second explains key options and defaults. It is front-loaded and efficient.

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 description explains the return value sufficiently for an agent to understand what to expect (DOM + OCR text, optionally PNG). Given no output schema, this is adequate. However, it does not cover error conditions or timeouts, which could be helpful.

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%, and the description adds meaningful context beyond the schema: it explains the default (text-only, zero image tokens), the effect of visual=true, and that headless mode defaults to true. This helps the agent select parameters correctly.

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 'Open a URL' and the resource 'browser', and specifies the return value as 'page context (DOM elements + OCR text)'. This distinguishes it from siblings like browser_click or browser_screenshot.

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 explains the default text-only mode and how to enable visual output, but does not explicitly state when to use this tool instead of alternatives like browser_read or browser_screenshot. The context is clear but lacks explicit when-not-to-use guidance.

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