browser_navigate

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

The description discloses that the tool keeps BiDi listeners active, which is not captured in the readOnlyHint=false annotation. This is valuable behavioral context beyond what annotations provide.

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?

A single sentence that is front-loaded with the core action and context, containing no unnecessary words.

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 simple navigation tool with one parameter and an output schema, the description covers the essential behavioral nuance (BiDi listeners) and session context. No additional details are needed.

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 100% with a good description for the url parameter (https:// prepending). The tool description does not add extra parameter information, which is acceptable given the schema is thorough.

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 action (Navigate to a URL), the resource (URL), and the context (existing session). It also highlights a key behavioral distinction (keeps BiDi listeners active) that differentiates it from tools like browser_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?

The phrase 'in the existing session' implicitly guides the agent to use this tool when a browser session is already open, contrasting with browser_open which likely starts a new session. However, explicit alternatives are not named.

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