browser_start

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

With no annotations provided, the description carries the full behavioral disclosure burden. It mentions the return value but omits that starting a browser launches a process, has side effects, and likely needs to be paired with browser_stop; it also does not disclose failure modes or lifecycle behavior.

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 very concise: two short sentences with no filler, and the action and primary output are front-loaded. It sacrifices some behavioral context for brevity, but the structure itself is clean and direct.

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 8 parameters, no output schema, and no annotations, the description is too thin to make the tool fully actionable. It does not explain the shape of the returned WebSocket endpoints, what happens if both profile_id and profile_no are supplied, or that a profile must already exist before starting it.

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 schema already explains all 8 parameters, their enums, and defaults. The description adds no extra semantics beyond the return value, but the baseline of 3 is appropriate because the schema handles parameter meaning well.

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 ('Start') and a clear resource ('a browser profile'), and it states the key return value (WebSocket endpoints for Puppeteer/Selenium). It distinguishes the tool from obvious siblings like browser_stop and browser_active, though it does not explicitly name a sibling to differentiate from.

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 guidance is given on when to use this tool versus alternatives such as profile_create, browser_active, or browser_stop. The description does not mention prerequisites like an existing profile or that browser_stop is needed for cleanup.

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