browser_select

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

No annotations are provided, so the description carries the full burden. It reveals the selection mechanism (value/label, snapshot ref/selector) but does not disclose side effects such as event dispatch, state changes, failure behavior, or whether selection replaces or requires existing page state.

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 concise sentences with the core action front-loaded. Every phrase earns its place, and there is no filler or redundant restating of parameter names.

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 tool with four optional, undocumented parameters and no annotations or output schema, the description is too thin. Missing guidance on parameter relationships, required conditions, and expected behavior leaves an agent to guess how to invoke it 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 description coverage is 0%, so the description must compensate. It adds meaning by mapping label/value to selection criteria and ref/selector to target location, but it does not explain whether the parameters are mutually exclusive, optional in combination, or how precedence works when both are supplied.

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?

States a specific action and resource: 'Select an <option> by value or label.' This distinguishes it from sibling interaction tools like browser_click or browser_fill, since selecting a dropdown option is a distinct operation.

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 implies usage by mentioning targeting via 'a snapshot ref or a selector,' but it does not explicitly say when to prefer this tool over browser_click or other siblings, nor does it mention exclusions or prerequisites such as needing a navigated page or a rendered select element.

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