Open New Tab

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

The description adds significant behavioral context beyond annotations: it notes the external origin contact and credential sensitivity, and mentions the need to close the tab after use. This aligns with openWorldHint true and readOnlyHint false annotations.

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, using four short sentences with clear sections (use case, preconditions, next steps, sensitivity). Every sentence adds value; no redundancy.

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 description covers the tool's role, preconditions, and sensitivity, but omits explanation of the 'waitUntil' parameter behavior. Since an output schema exists, return values need not be described. The gap on parameter semantics prevents a perfect score.

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?

With 0% schema description coverage, the description must compensate. It adds context for the 'url' parameter (must be authorized), but provides no explanation for the 'waitUntil' enum. This partial coverage earns a middle score.

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 tool's purpose: opening a new tab when a separate page is needed, distinguishing it from browser_navigate which uses the existing tab. The verb 'open' and resource 'new tab' are explicit.

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 provides explicit when-to-use guidance ('when a full-profile reproduction genuinely requires a separate page'), preconditions (active browser context, authorized URL), and next steps (inspect/trace then close). It also contrasts with the sibling tool browser_navigate by implication.

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