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. 'Navigate to a URL' is essentially a restatement of the tool name and provides no details about page load behavior, tab routing, failure handling, or side effects. It exceeds the minimal transparency seen in 'Process' descriptions.

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 extremely brief and under-specified. While it contains no wasted words, it does not earn its place by providing sufficient information for a navigation tool. The three-word sentence lacks the balance of conciseness and informativeness seen in higher-scoring examples.

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 navigation tool with 2 parameters and no output schema, the description is incomplete. It omits mention of tab targeting, waits for page load, error behavior, and relationship to sibling tools. The schema helps, but the description alone does not give an agent enough context to use the tool 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 100%: both 'url' and 'tabId' are described in the input schema, including optional behavior and reference to browser_list_tabs. The description adds no extra parameter semantics, 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 resource 'URL', clearly indicating the primary function. It distinguishes from sibling tools like browser_close_tab or browser_click, though it doesn't explicitly differentiate from related navigation tools like browser_open_tab or browser_go_back/forward.

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 provides no guidance on when to use this tool versus alternatives. The input schema mentions tabId and references browser_list_tabs, but the description itself offers no context or exclusions. Agents receive no situational cues for selecting this over other browser navigation tools.

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