browser_tab_new

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 does reveal one non-obvious behavior — the tab is auto-assigned to the active task group — but omits whether the tab becomes focused, what happens with no active group, and whether the tool returns a tab handle.

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?

Two short sentences with no filler, and the core action is front-loaded. It is efficient but arguably under-specified rather than tight.

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 tool with no annotations and no output schema, the description should say what the call returns (e.g., a tab identifier) so the agent can chain it to browser_tab_select or browser_text. That and the optional-parameter behavior are both missing.

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 description coverage is 0% for the single optional 'url' parameter, so the description must compensate and does not. It never says that url may be omitted to create a blank tab, nor what happens when a url is supplied (navigation vs. preload).

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 and resource ('Open a new tab'), which is unambiguous on its own. However, it does not differentiate itself from the sibling browser_open, leaving the agent to guess which one creates a tab versus a window/navigation.

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?

No guidance on when to use this versus browser_open, browser_tab_select, or browser_group_begin. The second sentence describes a side effect (joining the active task group), not a usage condition or prerequisite.

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