Open a new browser tab, optionally load a URL, and focus it immediately so AI coding assistants can inspect or interact with the page.
Open a new browser tab, optionally navigate to an initial URL, and automatically set active focus.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Initial URL to open in the new tab | about:blank |
| setActive | No | Whether to make the new tab active immediately (default: true) | |
| waitUntil | No | Navigation wait condition | domcontentloaded |
Changes observed during successful MCP inspections.
v0.17.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It does disclose that focus is set automatically and that navigation is optional, but it omits side effects on existing tabs, whether a browser must already be running, and whether the call is idempotent. Useful but incomplete for a state-changing browser action.
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 front-loaded sentence with zero filler; the verb and resource lead, and the two optional behaviors follow compactly.
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 simple 3-optional-parameter tool this covers the essentials, but with no output schema and no annotations the description should say what the call returns (e.g., a tab identifier usable with switch_tab/close_tab) and what session state it requires. Those gaps leave an agent guessing about follow-up steps.
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 schema already documents all three parameters and the waitUntil enum. The description only echoes 'url' and 'setActive' in prose and adds no format or default detail beyond what the schema provides; baseline 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 names a specific verb and resource ('Open a new browser tab') and adds the two notable behaviors (optional initial URL, automatic focus). It is clearly distinguishable from close_tab/switch_tab by the verb, though it never explicitly contrasts itself with siblings like vibeside_navigate, which also takes a URL.
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?
There is no guidance on when to create a new tab versus navigating the current one (vibeside_navigate) or switching to an existing tab (vibeside_switch_tab) — a genuinely ambiguous choice in this toolset. No prerequisites (e.g., an active browser session) are stated either.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.