browser_select_option

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

No annotations are supplied, so the description carries the full burden, yet it only states the target ('active or specified tab'). It says nothing about whether the action waits for the element, fires change events, handles disabled or multi-select options, or what happens on failure. For a UI-mutating browser automation tool with zero annotation coverage, this is a substantial gap.

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?

A single front-loaded sentence with no filler; the resource and target scope appear immediately. Nothing could be trimmed without losing content.

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?

With five optional parameters, no annotations, and no output schema, the description leaves the key calling ambiguity unresolved: whether to identify the element by ref or CSS selector and whether to select by visible text or value. It is minimally viable but not complete for an agent that must choose among these combinations.

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 all five parameters are already documented, which sets the baseline at 3. The description's 'active or specified tab' merely restates that tabId is optional and adds nothing about how ref vs. selector or text vs. value should be chosen when zero parameters are required.

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?

Names a specific verb ('Selects') and resource ('an option from a <select> dropdown or listbox'), which is enough to distinguish it from browser_click or browser_set_checked. It doesn't explicitly say how it differs from those siblings, keeping it short of a 5.

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 phrase '<select> dropdown or listbox' implicitly scopes usage to native select elements, implying browser_click for custom widgets, but this is left for the agent to infer. There is no explicit when-not guidance or named alternative, so usage is only implied.

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