chrome_launch

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

No annotations provided, so description carries full burden. It discloses that DevTools Protocol is enabled and that it can open a new tab, but omits key behaviors: what happens to existing Chrome instances, side effects (e.g., leftover processes), permission requirements, or response format. Incomplete for a launch tool.

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 short sentence, well front-loaded, but under-specifies. It sacrifices necessary detail for brevity, making it suboptimal for an agent to invoke correctly.

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 moderate complexity (browser launch with DevTools, 6 parameters, no output schema), the description is severely incomplete. It lacks return value details, error handling, parameter explanations, and any behavioral nuance beyond the basic action.

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 adds no parameter information. All six parameters (url, waitMs, debugUrl, extraArgs, chromePath, userDataDir) are completely undocumented, leaving the agent blind to their meanings and 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 clearly states that the tool launches a Chrome window with DevTools enabled or opens a new tab if already running. This provides a specific verb and resource, and hints at dual behavior, which distinguishes it from siblings like chrome_navigate, though not fully from chrome_open_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?

The description implies when to use (launch new vs open tab) but gives no explicit guidance on when not to use or alternatives. Among siblings like chrome_open_tab, there is no differentiation advice, leaving the agent to guess.

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