navigate

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

The description discloses important behavioral traits: it opens a bundled Chromium session if none exists, returns handles, follows redirects, reports the final identity, and identifies bot walls, CAPTCHAs, and login walls so blocked requests are surfaced as blocked rather than as timeouts or empty pages. It also notes it waits for the load state. These details go beyond the minimal readOnlyHint annotation and provide useful context for the agent.

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 efficient: it front-loads the core actions, then adds the first-call behavior and return values in a compact manner. Every sentence adds value, and there is no redundant or filler content.

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 there is no output schema, the description does a good job of explaining what the tool returns (final identity, HTTP status, robots.txt advisory, block verdict). It also covers the session-opening scenario and error handling for blocked pages. However, it does not explain all parameters, notably timeout_ms, and does not address edge cases like navigation failures beyond the block detection. Still, it is quite complete for a navigation tool.

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 0%, so the description carries the burden of explaining parameters. It hints at 'url' (Go to a URL), 'action' (go back, forward, reload, stop), 'page' (with no `page`), and 'wait_until' (the load state you name), but it does not mention 'timeout_ms' at all, and it does not formally define the values or defaults. The description adds some meaning but is not comprehensive enough to fully compensate for the lack of schema documentation.

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 states a specific verb ('go to', 'go back', etc.) with a clear resource (URL, browser navigation) and distinguishes itself from siblings by being the first call that opens a session and returns session/page handles. It also names the return values (final identity, HTTP status, robots.txt advisory, block verdicts), making the tool's purpose unmistakable.

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 mentions 'Can be the FIRST call' as a usage context, implying when it should be used (to initiate a browser session), but it does not explicitly compare this tool to siblings like wait_for, scroll, or manage_tabs, nor does it state when not to use it. The guidance is implicit rather than explicit.

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