scraping_browser_navigate

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, and the description adds nothing beyond stating the action. It does not say whether the call blocks until the page loads, what happens when a session is missing or navigation fails, or how the optional country parameter alters the session's egress. Note that navigation mutates browser state, which sits awkwardly with readOnlyHint, though it destroys no data; this is a mild tension, not a contradiction.

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?

It's a single front-loaded sentence with no filler, and the verb and resource come first. It is arguably too terse rather than padded, but on conciseness it is clean.

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 stateful browser-navigation tool that has no output schema, the description should mention the existing-session prerequisite, the blocking or loading behavior, and the typical follow-up tool. None of that is present, so an agent must infer the session lifecycle entirely from the tool's name.

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%: both url and country are documented in the input schema, including the URL pattern and ISO country examples. The description adds no meaning beyond that, so the baseline of 3 applies when the schema does the work.

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: navigate a scraping browser session to a new URL. That distinguishes it from the sibling navigation tools scraping_browser_go_back and scraping_browser_go_forward, which move through history, and from the scrape_* tools, which fetch content. It does not say the tool also accepts an optional country routing parameter, but the core action is unambiguous.

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 gives no when-to-use guidance: it does not say a browser session must already exist, when to choose this over scrape_as_markdown, or what to do after navigating, such as calling scraping_browser_snapshot. The name implies that this tool is stateful and belongs to a browser session, but the description states nothing about that.

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