Browser navigate

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

With no annotations, the description carries the burden of behavioral disclosure. It warns that navigation may reload the page and lose SPA in-memory state, which is crucial context. However, it does not disclose other behaviors such as how wait_until affects navigation or what happens on cross-origin attempts beyond the 'same-origin' constraint.

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, with the purpose front-loaded and every sentence earning its place. It is concise, clear, and free of unnecessary verbosity.

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 covers the core function and key caveat, but it omits parameter explanations and return behavior. Since there is no output schema, more detail about expected outcomes and parameter usage would improve completeness. It is adequate but has clear 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 0%, and the description does not explain any of the four parameters (url, path, session_id, wait_until). It only hints at same-origin navigation but provides no parameter-specific semantics, leaving the agent without the needed guidance.

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 action ('Perform same-origin full page navigation') and identifies the specific resource ('browser debug session'). It also distinguishes from a sibling tool by explicitly mentioning browser_click for SPA route changes, making the purpose 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?

It provides explicit usage guidance by warning about state loss and directing users to prefer browser_click for SPA route changes. This clearly indicates when this tool is appropriate (full page navigation) versus an alternative.

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