browser_navigate

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

With no annotations, the description carries the behavioral burden and does so well: it discloses the tab-group creation/use side effect, alias behavior, and dedicated-window separation. It does not mention whether navigation waits for page load or returns status, but those are conventional and less critical for a navigate operation.

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?

Three sentences with no filler: the core action is first, then the non-obvious task-group behavior, then aliases and window handling. Every clause earns its place.

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 7-parameter tool with no annotations and no output schema, the description covers the non-obvious interaction behaviors (tab groups, parallel task naming, dedicated windows). It does not explicitly discuss new_tab/new_window or how to obtain window_id via browser_ensure_window, though the schema covers those details.

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%, so the baseline is 3, but the description adds real value beyond the schema by explaining the task parameter's tab-group effect, the MUST-use-different-names constraint for parallel tasks, and the alias relationships. This materially helps an agent set parameters correctly.

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?

Opens with 'Navigate to a URL', a specific verb and resource, and the tab-group/window details make the tool's role unmistakable. It is easily distinguished from siblings like browser_fetch or browser_switch_tab because the core action is explicit.

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 gives clear guidance on task names for parallel tasks and window isolation, but it never names alternatives or states when not to use this tool. Selection guidance is implied by the tool name and 'Navigate to a URL' rather than explicitly contrasted with sibling tools like browser_fetch.

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