Navigate

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

Annotations already convey non-readOnly and openWorld traits, so the description's minimal disclosure is partially mitigated. It adds that a snapshot is returned, but does not mention side effects like changing the current tab or loading behavior. This is acceptable but not rich.

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?

Two short sentences, no redundant wording, and the key actions are front-loaded. Every word earns its place.

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 simplicity, the description is minimally sufficient, but it lacks guidance relative to sibling tools and does not describe the snapshot output format or any prerequisites. Schema and annotations fill in many details, leaving some gaps.

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 high (83%), so the parameters are already well-documented. The description adds no extra meaning beyond the schema, such as clarifying the behavior of `direction` or `tabIndex`. Baseline 3 applies.

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 tool's function: go to a URL or move through history, and returns a page snapshot. This is a specific verb+resource+outcome, but it does not explicitly distinguish from sibling tools like browser_snapshot or browser_tabs, though the navigation intent is evident.

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?

No guidance is provided on when to use this tool versus alternatives. Given many sibling browser tools exist, an agent would not know whether to use browser_navigate, browser_connect, or browser_tabs for a given task. The description solely states what it does, not when to choose it.

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