browser_open

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

Annotations already indicate readOnly=false and destructiveHint=true, so the description builds on them by adding that the window is temporary and that the URL must be user-authorized. This goes beyond the structured annotations and does not contradict any of them.

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 the core action, followed by isolation and authorization guidance. Every sentence adds meaningful information and there is 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 one-parameter tool with no output schema, the description covers purpose, standout behavioral traits, and URL authorization. It does not state what value is returned or how the temporary window is tracked later, but this is minor given the sibling context and simplicity.

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, the description compensates by framing the 'url' parameter as requiring user authorization, adding meaning beyond the bare 'string + uri' schema. It could go further by explaining constraints on the URL value, but what is present is genuinely useful.

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 clear verb ('Open') and resource ('dedicated, temporary Chromium window'), and distinguishes itself from siblings by stating it does not attach to personal browser tabs. This gives an agent enough to understand exactly what the tool does and how it differs from browser_status, browser_click, etc.

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 provides clear context for using the tool: a temporary window, isolated from personal browser tabs, with a user-authorized URL. It does not explicitly name alternatives or exclusion conditions, but the context is strong enough for typical agent selection.

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