browser_launch

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the profile is persistent and that the browser is headed by default, but it omits behavior such as what happens if a browser is already running, whether it blocks until ready, or what session handle is returned.

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?

A single, front-loaded sentence with no wasted words. The parenthetical efficiently covers the key default and override.

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 simple launch tool with one parameter and no annotations, the description covers purpose and the headless option. However, it lacks context about launch lifecycle, session identity, and interaction with existing browser sessions, which an agent needs to invoke it reliably.

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 coverage is 0%, but the description compensates by explaining the sole parameter: headless defaults to false and should be passed as true for headless mode. The only gap is that additionalProperties is true, and the description does not mention other accepted options.

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 gives a specific verb and resource: 'Launch the browser with a persistent profile.' This clearly distinguishes it from browser_navigate, browser_close, and other browser interaction tools, though it does not explicitly name alternatives.

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 explains the headless parameter default but gives no guidance on when to call browser_launch versus browser_navigate or other sibling tools. It implies a launch step is needed but does not state prerequisites or sequencing.

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