browser_open

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds the useful 'reattach' behavior and 'managed' context, but it does not explain side effects, cleanup, or what happens on repeated calls beyond reattaching.

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 concise sentence with no filler. It front-loads the core action and resource and contains only information that helps characterize the tool.

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 simple optional-parameter tool with rich schema and annotations, the description is largely adequate. However, with no output schema, it does not mention what the tool returns or how the 'reattach' behavior relates to the supplied url parameter, leaving a minor but real gap.

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 description coverage is 100%, so the schema fully documents url, mode, and devTools. The description adds no additional parameter-level meaning, so it stays at the baseline and does not compensate beyond the schema.

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 specific verbs ('Launch or reattach') plus a clear resource ('managed headful/interactive browser session'). It clearly identifies the tool's operation and is distinct from the sibling task/schedule/cabinet tools, even without naming a browser-specific alternative.

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 intended use is implied by the name and description, but there is no explicit statement about when to use this tool versus alternatives, nor any preconditions such as requiring the VNC stack. An agent gets only indirect routing guidance.

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