browser_new_tab

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

No annotations provided; description explains that the tool opens and switches to a new tab and that subsequent tools operate on it. Lacks details on whether it creates a new window or tab, but is adequate for a simple 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?

Two sentences: first states action and effect, second provides use cases. Front-loaded and no extraneous text.

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 simple tool (1 param, no output schema), description covers main purpose and use cases. Minor gap: no mention of return value or behavior when no URL is provided.

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% with one optional 'url' parameter. Description repeats 'Optional URL' without adding new semantics like default behavior.

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?

Description clearly states the tool opens a new browser tab and switches focus to it, with specific use cases (OAuth popups, payment redirects, cross-tab verification). This distinguishes it from siblings like browser_switch_tab.

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?

Explicitly lists scenarios for use (OAuth, payment redirects, cross-tab verification), implying context. Does not explicitly state when not to use, but the sibling list provides alternatives.

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