Open browser debug session

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

With no annotations, the description carries the burden of behavioral disclosure. It states the browser is isolated and that CDP endpoints are returned, providing some clarity. However, it omits crucial details such as session lifecycle, requirement for approval tokens, or whether resources need cleanup via close_debug_session.

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, tightly worded sentence that front-loads the action and clearly states the purpose. Every word contributes value, with no redundancy or filler.

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 tool with 9 parameters, no annotations, and no output schema, the description is far too sparse. It does not explain parameter semantics, the meaning of CDP endpoints for downstream use, or the need to close the session. Complex behavior and side effects are left unaddressed, making the tool difficult to invoke correctly.

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 coverage is 0% and the description does not explain any of the 9 parameters. While 'local frontend deployment' hints at deployment_id, features like browser_id, viewport dimensions, open_devtools, and approval_token are entirely undocumented. The description fails to compensate for the lack of schema descriptions.

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 ('Open') and identifies both the resource ('local frontend deployment') and the outcome ('return CDP WebSocket endpoints'). It clearly distinguishes from siblings like close_debug_session or browser_navigate by focusing on creating an isolated browser session for debugging.

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 description implies the tool is for debugging local frontend deployments in isolation, but it does not explicitly state when to use this versus alternatives such as create_debug_session or list_browser_targets. No exclusions or alternative recommendations are provided, so guidance is only implied.

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