chrome_open_new_tab

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not specify whether the new tab becomes active, whether the URL is loaded asynchronously, what happens with invalid URLs, or what the return value indicates. The description is minimal and lacks these details.

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 a single sentence and front-loads the core action. However, it repeats information already present in the schema ('optionally with a URL'). It is concise, but not exceptionally informative beyond the schema.

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 the tool's simplicity (one optional parameter, no output schema), the description adequately covers the basic purpose. However, it leaves open questions about return values, tab focus behavior, and error handling. It is minimally viable but not complete for an agent that might need behavioral details.

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?

The input schema already provides 100% coverage with the parameter description 'Optional URL to open in the new tab'. The tool description merely restates this as 'optionally with a URL', adding no extra semantic detail. Baseline 3 is appropriate as the schema does the heavy lifting.

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 action ('Open a new tab in Chrome') and resource (Chrome tabs). It distinguishes from siblings like chrome_navigate (navigate existing tab) and chrome_close_tab (close tab) by specifying 'new tab'. Very clear and specific.

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 does not provide guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It simply states what the tool does. No mention of when to choose this over chrome_navigate or how it fits into a broader workflow.

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