browser_navigate

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the core actions but does not reveal whether navigation waits for page load, how errors are reported, or side effects on browser history. These are relevant for an agent invoking the tool repeatedly.

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 a single, front-loaded sentence that lists every action without redundant wording. It is concise, scannable, and every word contributes to understanding the tool's scope.

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 tool is simple, with two well-documented parameters and an enum, and the description covers all actions. However, with no output schema, it omits information about return values or failure behavior, which are important for an agent to verify success. It is adequate but not fully complete for context.

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?

The input schema already fully describes both parameters, including the action enum and the URL description. The tool description adds no additional parameter-level meaning beyond what the schema provides, so the baseline of 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 uses a specific verb 'Navigate' and clearly enumerates the supported actions: URL, back, forward, and reload. This unambiguously distinguishes the tool from sibling browser tools like browser_tabs or browser_snapshot, which handle different concerns.

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 implies when to use the tool (for page-level navigation) but provides no explicit alternatives or exclusions. It doesn't mention when to use browser_tabs or browser_window instead, leaving the agent to infer the appropriate context from the action list alone.

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