launch_browser

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action and configuration options, but does not disclose side effects, default headless behavior, whether a browser session handle is returned, whether multiple instances are allowed, or common failure conditions.

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 with no filler. It front-loads the action and resource, and the trailing option list is compact yet informative.

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 tool is easy to invoke because all parameters are optional and the schema documents defaults and enums. However, with no output schema and no annotations, the description does not explain what the tool returns or how the launched browser connects to sibling tools, leaving a moderate completeness 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 100%, so the baseline is 3. The description mostly paraphrases the schema properties (browser enum, headless, viewport dimensions, proxy, args) and adds no new constraints, format details, or edge-case semantics beyond what the schema already provides.

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, 'launch', with a clear resource, 'browser instance', and names the supported browsers (Chrome, Firefox, Edge). This clearly distinguishes it from siblings like close_browser, navigate, and get_current_url.

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 explicit when-to-use or alternative guidance is provided. The verb 'launch' implies this is the initial step before other browser operations, but the description does not state that ordering, mention 'use before navigate', or rule out cases where launching is unnecessary.

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