navigate

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

With no annotations provided, the description must disclose behavioral traits, but it only states the action without mentioning side effects (e.g., changing the current page), wait behavior, or return values. The existence of waitUntil and clearConsole/clearNetwork parameters is not surfaced in the description, leaving the agent without crucial behavioral context.

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, clear sentence with no redundant words. It is appropriately sized for a simple navigation tool and front-loads the core action immediately.

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 has moderate complexity (4 parameters, 1 enum) and no output schema or annotations. The description covers the core action but lacks explanation of behavioral context like waitUntil semantics or log-clearing options. The schema compensates for parameter details, but overall completeness is minimal yet adequate.

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 covers 100% of parameters, each with a description, so the schema carries the full semantic load. The tool description adds no additional parameter meaning beyond what the schema already provides, placing it at the baseline for complete schema coverage.

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 the specific verb 'navigate' and clearly identifies the resource ('a URL in the browser'), making its purpose explicit. It is distinguishable from sibling tools such as click, type, screenshot, and network_requests, as navigation is a distinct action.

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 the tool is used when you want to change the browser's current URL, but it provides no explicit guidance on when to use it versus alternatives, nor any exclusions or prerequisites. It relies on the tool name and common sense rather than stating usage context.

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