open_in_browser

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

Discloses that tabs close by default and indicates optional behaviors (extract content, screenshot). However, no annotations are present, so the description carries the burden; it does not cover other behavioral aspects like authentication or rate limits.

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 sentences, front-loaded with action, and concise. No wasted words.

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?

No output schema or annotations; description does not explain return values, error behavior, or result format for extracted content or screenshots. Incomplete for a tool with 7 parameters and complex output.

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?

With 0% schema description coverage, description adds meaning for extract_content and screenshot booleans and default tab closing behavior, but fails to explain host, port, wait_ms, or keep_open beyond what schema defaults imply.

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 tool opens a URL in Chrome via CDP with optional DOM extraction and screenshot. It distinguishes the primary action from siblings like extract_content or navigate_and_read, but does not explicitly differentiate from them.

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 on when to use this tool versus alternatives (e.g., extract_content, navigate_and_read). No mention of prerequisites or when not to use.

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