browser_open

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

With no annotations, the description carries the full burden, and it does disclose one important behavior: the call blocks until load completes, and it targets the task tab with an active-tab fallback. It says nothing about timeout behavior, navigation failure, or whether it can leave the page in a partially loaded state.

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?

One sentence, front-loaded with the action and target, with the blocking behavior appended as a qualifier. Nothing extraneous.

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 one-parameter navigation tool with no output schema and no annotations, the description covers the essentials: what it navigates, which tab, and that it waits for load. Only failure/timeout semantics are missing, which is a minor gap at this complexity.

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% and the single parameter has no description in the schema, so the description must compensate. It does connect the one parameter to a URL concept, but adds no meaning about accepted schemes, absolute vs relative URLs, or what happens with redirects — leaving the format underspecified.

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?

States a specific verb+resource ('Navigate ... tab ... to a URL') and scopes the target as the task tab or active tab, which distinguishes it from browser_tab_new and browser_tab_select. It is clear what the tool does, though it never names the sibling navigation-adjacent tools it supersedes.

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?

Usage is only implied: an agent can infer this is the tool for loading a page, and that tab creation/selection belongs to browser_tab_new/browser_tab_select. There is no explicit statement of when to use it, when not to, or that a tab fallback exists only when no task tab is present.

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