browser_launch

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

With no annotations, the description carries full behavioral disclosure. It does disclose the notable trait 'remote debugging enabled' and that this creates a new instance, but it does not say whether the call returns connection info, whether it blocks, or how the instance is cleaned up.

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 sentence with no extraneous words, and the key facts (launch, new, remote debugging) appear immediately. Every element contributes to selecting or invoking the tool.

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 zero-parameter, no-output-schema tool, the description is largely sufficient: it identifies the action and its distinguishing mode. The main gap is surrounding lifecycle/cleanup guidance, but that is less critical for a parameterless launch 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?

The tool has zero parameters, so there are no argument semantics for the description to clarify. The description accurately describes what the parameterless call accomplishes.

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 names a specific action ('Launch'), a resource ('new Chrome browser instance'), and a key mode ('remote debugging enabled'). This makes it easy to distinguish from siblings like browser_connect, which imply attaching to an existing instance.

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 word 'new' implies this is for starting a fresh browser rather than connecting to an existing one, but the description never explicitly says when to use this instead of browser_connect or how to confirm the instance is ready. Usage is implied rather than stated.

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