CDP: New

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety profile is covered. The description adds useful behavioral context beyond that: it opens a completely fresh, isolated browser with its own profile and automatically allocated debug port, which tells the agent it won't disturb existing sessions.

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?

Two tightly written sentences with zero waste. The core action and key distinction between reusable and throwaway profiles are both front-loaded.

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?

The description covers the launch behavior and profile choice, and annotations cover the safety profile. However, with no output schema, it does not explain what the tool returns (e.g., a target/session handle or debug port) or reference the sibling cdp_launched for discovering launched browsers, leaving a practical gap for an agent wiring this into a CDP workflow.

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 documents all six parameters. The description adds only a small clarification for `profile` (omitting it yields a throwaway session), which is helpful but not enough to lift this above the baseline of 3.

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?

States a specific verb ('Open') and resource ('browser'), and adds scope details: COMPLETELY FRESH, isolated, own profile, auto-allocated debug port. It does not explicitly differentiate from sibling cdp_launch, so it falls short of a 5.

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 only guidance is about the `profile` parameter ('Use `profile` for a reusable named profile, omit for throwaway'), not about when to choose cdp_new over alternatives like cdp_launch. No when-not-to-use or prerequisite conditions are given.

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