open_new_tab

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

No annotations are present, so the description carries the full burden. It discloses the optional navigation and switching behavior, but does not note what happens when url is null, whether the new tab is opened as a background tab when switch_to is false, or any side effects like accumulation of tabs. Basic behavior is covered, but richer context is missing.

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?

A single sentence that is front-loaded with the action and includes both optional behaviors with no filler. Efficient and scannable.

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 simple two-parameter optional tool with an output schema, the description covers the essential call semantics. It lacks details on default switching behavior (though the schema supplies this) and edge cases, but an agent can infer the correct invocation. Missing usage guidance is the main gap.

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%, so the description must compensate. It maps both parameters to behavior: 'navigating' corresponds to url and 'switching' to switch_to, giving semantic meaning beyond property names. It does not explicitly name the properties or explain null-URL behavior, but the mapping is clear and the schema provides defaults.

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 uses a specific verb ('Open'), names the resource ('new browser tab'), and specifies the optional actions ('navigating and switching to it'). It is clearly distinct from sibling tab tools such as switch_to_tab and close_active_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?

No guidance on when to use this tool versus siblings like navigate, switch_to_tab, or switch_to_newest_tab. There are no exclusions, prerequisites, or alternative recommendations, leaving the agent to infer the appropriate context.

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