new_tab

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

No annotations are provided, so the description carries the full burden. It doesn't say whether the new tab becomes the active/focused tab, what happens if url is omitted (blank tab?), or whether the call is reversible/closable. 'Open a new tab' restates the name without adding behavioral context.

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?

One short sentence with zero waste and no front-loading problem, but the brevity comes at the cost of missing specification rather than from disciplined compression. Adequate as a label, not as documentation.

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?

With no annotations, no output schema, and an optional undocumented parameter, the description is the only source of behavioral information and supplies almost none. An agent cannot determine tab focus behavior or the blank-tab case before invoking.

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 0% and the single parameter (url) is not referenced in the description. Critically, url is optional, and the description does not explain the no-url case. With only one self-evident parameter, the gap is small but real, and the description does not compensate for it.

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+resource ('Open a new tab'), which an agent can distinguish from the state-reading siblings like list_tabs or get_page. However it does nothing to separate itself from switch_tab or navigate, which are the closest siblings and are the most likely to be confused with it.

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 when-to-use guidance at all. In a sibling set containing navigate, switch_tab, close_tab and list_tabs, the agent gets no signal on when opening a new tab is preferred over navigating the current one or switching to an existing tab.

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