flow_launch_browser

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

With no annotations, the description carries the full burden of behavioral disclosure. It doesn't say whether launching replaces or attaches to an existing browser session, what the default lifecycle is, whether authentication state persists, or what happens if the debug port is already in use.

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 sentence with no filler, and the mode distinction is front-loaded. It is efficient, though it could have spent the same length on more useful behavioral detail.

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 session-launching operation with no annotations and no output schema, the description omits critical context: side effects on any running browser, return behavior, and cleanup expectations. The schema covers parameters but the description leaves lifecycle behavior unspecified.

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 port, headed, and targetUrl are fully documented in the schema. The description's headless/headed contrast duplicates the schema's 'headed' description and adds no new syntax, format, or defaulting detail.

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 states it 'controls local browser execution mode' and clarifies the headless-vs-headed distinction, but the verb 'controls' is vague and it never says it launches the browser (as the name flow_launch_browser implies). An agent must infer that this starts/stops a browser session rather than reconfiguring one.

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?

It implies when headed mode is needed ('for 1-time login'), which gives some usage context, but it never states when to call this tool versus siblings like flow_open_tab or flow_status, nor any prerequisites or exclusions.

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