browser_open

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

Without annotations, the description carries the full burden. It discloses that it returns a JPEG screenshot and handles both opening and navigating, but lacks details on screenshot scope (full page vs viewport), potential side effects, or required permissions.

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 sentence with no fluff, but it could be structured to separate the two use cases (opening vs navigating) for clarity. Still 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?

Given the tool's complexity (2 params, many sibling tools, no output schema), the description covers basic functionality but misses usage guidance, parameter details, and comprehensive behavioral traits, leaving gaps for an AI agent.

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 the description must compensate. It mentions 'at the given URL' (referring to url param) but does not explain the required 'id' parameter (likely sandbox identifier) or its format. Incomplete parameter documentation.

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 or navigates Chrome in a sandbox at a given URL and returns a JPEG screenshot, specifying verb, resource, and outcome, distinguishing it from siblings like browser_navigate or browser_snapshot.

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 explicit guidance on when to use this tool versus alternatives such as browser_navigate (if only navigation is needed) or browser_snapshot (if only a screenshot is needed). No prerequisites mentioned, e.g., sandbox must be running.

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