browser_new_tab

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

With no annotations, the description carries full burden. It does not disclose whether the new tab becomes active, remains in background, or if the session must already exist (though implied by schema). No return value or side effects are mentioned, leaving significant gaps in behavioral understanding.

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 concise at five words, which is appropriate for a simple tool. However, it could incorporate more context without becoming verbose, such as mentioning session_id or optional URL. It is not overly terse but misses opportunities.

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?

Given the availability of an output schema and many sibling browser tools, the description is incomplete. It fails to explain core behaviors (e.g., does the tool switch to the new tab?) or how it differs from browser_open and browser_switch_tab. The output schema is present but not described, so the agent relies solely on the minimal text.

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 100%, so the baseline is 3. The description adds no extra meaning beyond the schema; it neither clarifies parameter usage nor provides examples. It is adequate but not contributing additional semantic value.

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 'Open a new browser tab' clearly specifies the action (open) and resource (browser tab), distinguishing it from siblings like browser_open (new window) and browser_switch_tab. However, it does not explicitly differentiate from similar operations, such as opening a tab versus switching, which could be clarified.

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 usage guidance is provided. The description lacks context about when to use this tool versus alternatives like browser_open, browser_switch_tab, or browser_navigate. An agent would need to infer based on names alone, which is insufficient.

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