start

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It states 'cold-launch real Chrome' which indicates a real process launch, but it does not disclose side effects like profile directory creation, resource usage, or what happens if a session already exists. For a mutation tool with no annotation support, this is a significant gap.

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, concise sentence that captures the core purpose without any extraneous content. It is front-loaded with the primary action and efficiently conveys the essence of 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 start operation, the description is adequate but lacks explicit details about session conflict handling, return values, or error conditions. Given there is no output schema, the description could benefit from mentioning what happens if a session already exists or how to confirm success. It meets the minimum bar but leaves gaps.

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% across all 6 parameters, each with detailed descriptions. The tool description itself adds no additional parameter semantics beyond the schema, so the baseline of 3 is appropriate. The description does not need to duplicate schema information.

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 clearly states the action: 'Start a browser session' and adds specificity with 'cold-launch real Chrome', which differentiates it from warm-start or in-process operations. It is not a tautology and gives a distinct operational profile that separates it from sibling tools like session_new.

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 provided on when to use this tool versus alternatives such as session_new or session_use. The description implies this is the entry point to launch a browser, but it does not explicitly state when it should be called, when it shouldn't, or mention available alternatives. Only implied context exists.

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