browser_navigate

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

No annotations are provided, so the description carries the full disclosure burden. It hints that it operates on a 'shared tab' but does not say whether navigation blocks until load completes, how it interacts with existing page state, or what happens on failure.

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 compact sentence that front-loads the primary use case (URL) before the secondary modes. No wasted words, though the brevity contributes to the underspecification elsewhere.

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?

With no annotations and no output schema, the description should do more. It covers the surface actions but leaves unanswered how this differs from sibling navigation tools and how the two parameters interact, which an agent needs to call it correctly.

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 0%, so the description must compensate. It does name the URL target and the three enum actions, which map onto both parameters, but it omits any detail on URL format and never clarifies the mutual exclusivity or precedence between url and action.

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 gives a specific verb (navigate) plus resource (the shared tab) and enumerates the three non-URL modes (back, forward, reload). This is clear and distinct from most siblings, though it never contrasts itself with similar navigation-related tools like browser_open or browser_tab_new.

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 states what navigation actions exist but offers no guidance on when to reach for this tool versus alternatives such as browser_open or browser_tab_new. The choice between moving the current tab and opening a new one is left entirely to inference.

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