browser_select

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose how options are matched (by value or visible label), which is useful. However, it does not mention side effects, event triggering, failure behavior when no option matches, or whether the dropdown must be visible first.

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, tightly written sentence with no filler. The action and target are front-loaded, and every word adds meaning.

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 no annotations, no output schema, and 0% schema coverage, the description is too thin. It does not clarify how 'ref' and 'selector' relate to the target dropdown, whether the dropdown is located through a default active element, or how the 'value' parameter should be formatted when matching by label versus value.

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 partially explains the 'value' parameter by saying options can be selected by value or visible label, but it gives no meaning for 'ref' or 'selector', leaving the agent to guess how to target the specific dropdown.

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 states a specific verb ('Select'), a precise resource ('an option in a <select> dropdown'), and the method ('by value or visible label'). It clearly distinguishes itself from sibling tools like browser_click and browser_fill by naming the exact element type and action.

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 case is implied: use this when you need to choose an option in a dropdown. However, it does not explicitly state when NOT to use it or mention alternatives such as browser_fill or browser_click, so guidance on tool selection is left to inference.

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