new_tab

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

No annotations are provided, so the description carries full burden. It says 'controlled tab' (implying browser automation context) and that it becomes active, but doesn't disclose side effects like what happens to the previous active tab, whether tabs are tracked, or what 'controlled' means operationally. 'Creating a tab' implies it won't destroy anything, but this is inferred rather than stated.

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?

Single sentence, zero waste. Every element earns its place: creation, control, optional URL, active-tab behavior. Front-loaded with the primary verb and action.

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?

The tool is relatively simple with one optional parameter and no output schema. The description covers the core behavior well. However, with no annotations, some behavioral context is missing - specifically the operational meaning of 'controlled' and whether opening a new tab has implications for the session. Given simplicity, this is adequate but could clarify tab lifecycle behavior.

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% for the single param, so baseline is 3. The description adds value by clarifying that the URL is optional and that the tool navigates to it as part of tab creation, which is meaningfully more than the schema's 'Optional URL to open.'

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 clearly states the verb (Create), resource (controlled tab), and primary action (make it the active tab). It mentions optional URL navigation. However, it doesn't explicitly distinguish from sibling tools like list_tabs, goto, or claim_tab, though the core purpose is clear enough.

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?

The description implies this is for opening a new tab versus navigating an existing one (goto), but doesn't explicitly state when to use this vs alternatives. No exclusions or when-not-to-use guidance. The contrast with goto is implied but not stated.

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