open_browser

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

No annotations provided, so description carries full burden. It mentions creating a WebDriver, registering it, and the need to pass session_id. However, it does not mention potential browser compatibility issues or resource usage.

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?

Well-structured with sections (Purpose, Typical Agent Workflow, Parameters, Returns, Note). Front-loaded with key information. Could be slightly more concise but overall efficient.

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?

Input schema has 2 optional simple parameters, no output schema. Description explains parameters fully, provides return structure, and gives a clear workflow. Adequate for an agent to use this tool 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%, so description compensates. It explains 'browser' as type to launch (default 'chrome') and 'headless' as running without visible window. However, it does not list possible browser values (e.g., 'firefox') or constraints.

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 it launches a new browser session, creates a Selenium WebDriver, and returns a session_id. This distinguishes it from sibling tools like close_browser or open_url.

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?

Provides a typical workflow (1. open_browser, 2. open_url, ...) and a note to call only once per workflow unless previous session closed. Also advises setting headless True in headless environments.

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