启动浏览器

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

由于没有提供任何注解，描述必须承担全部行为说明责任。它明确说明了隔离 profile 不污染个人配置、开放远程调试端口、默认立即附加会话——这些都是有用的上下文。但未提及进程生命周期、清理行为、权限要求或端口冲突处理方式。

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?

单句结构紧凑，核心信息（隔离启动、调试端口、默认附加）前置，几乎没有冗余。信息密度高，但受限于句子过短，无法承载更多必要的使用指引。

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?

该工具参数多达 12 个且无注解、无输出 schema，描述仅覆盖了其中少数几个核心概念。虽然 schema 本身有 83% 的描述覆盖率可以弥补部分缺失，但对于如此复杂且具有副作用的启动操作，描述仍显得不够完整。

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 描述覆盖率为 83%，基线即为 3。描述中提到的 user-data-dir、调试端口和 attach 行为与 schema 中已有说明高度重合，未对 headless、keepProfile、watchAllTargets、targetId 等参数补充新的语义细节。

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?

明确给出了动词（启动）、资源（Chromium 浏览器）和关键属性（独立 user-data-dir、远程调试端口），足以将其与 browser_connect / browser_discover 等同类工具区分开来。但它没有像高质量定义那样点明具体的不适用场景或直接命名同类工具。

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?

描述仅隐含了使用该工具的情境（需要启动新浏览器时），没有明确说明何时应改用 browser_connect、browser_discover 或 browser_installed。默认 attach 行为提供了一点上下文，但未形成真正的使用指引。

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