browser_navigate

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

With no annotations, the description carries the burden. It does disclose that a refreshed accessibility snapshot is returned, which is useful. However, it does not mention potential side effects, wait behavior, or error handling, which could matter for navigation.

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 that efficiently communicates the action and expected result. No wasted 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?

The tool is simple, but the lack of annotations and output schema means the description should cover more. It does state the return type (accessibility snapshot), which is helpful, but omits details about loading behavior or error conditions. It is minimally adequate but not comprehensive.

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 67%: pageId and sessionId have descriptions, url does not. The description does not add meaning for url beyond the schema, but the parameter is self-explanatory. Overall, the description adds little but does not need to compensate heavily.

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 resource ('selected page'), and clearly states the outcome ('return its refreshed accessibility snapshot'). It distinguishes itself from sibling navigation tools like go_back and reload by focusing on URL-based navigation and the snapshot result.

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?

No guidance is provided on when to use this tool versus alternatives such as browser_go_back, browser_go_forward, or browser_reload. The usage is implied (navigate to a URL), but there are no explicit exclusions or alternative recommendations.

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