browser_navigate

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

No annotations, so the description carries the full burden and does so well: it discloses that the response reports the HTTP status and the actually-landed URL, warns that redirects to login walls or regional domains appear there, and flags that a 404/403 still returns a document that should not be read as content. It also states the default wait_until and that the two browsers share nothing.

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?

Purpose is front-loaded, then behavior, then parameter semantics. Four short paragraphs with essentially no filler; each sentence adds a distinct piece of operational value.

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?

Despite an output schema existing, the description usefully explains return semantics while covering defaults, parameter behavior, and failure modes. The only meaningful gap is the absence of any routing against browser_open.

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 0%, so the description must compensate, and it does: wait_until gets its default and per-value meaning, and browser gets its main/support distinction plus isolation semantics. Only url is left unexplained, which is self-evident.

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 and resource ('Go to a url in this browser's page') and adds the conditional 'opening it if none exists,' which hints at how it differs from browser_open. It never names the sibling, though, so an agent must infer the boundary between navigate and open.

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?

Offers strong guidance on parameter choice (when to use domcontentloaded vs load vs networkidle) and on browser isolation, but says nothing about when to choose this tool over browser_open. Usage guidance is parameter-level, not tool-selection-level.

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