select_option

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

With no annotations, the description must disclose behavioral traits. It does not explain that it clears previous selections, handles multi-select, or requires the element to be present on the page. The agent cannot infer side effects or constraints from this text.

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 (10 words) that conveys the core purpose efficiently. No redundant information. However, it might be too concise at the expense of clarity for some users.

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?

Given the tool's complexity (browser interaction, select elements) and lack of output schema/annotations, the description is inadequate. It omits details on how selectors work, how to handle multi-select, and what happens after selection. Completeness is low.

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 coverage is high (75%), so the description adds some value by explaining that values are matched by value or visible label. However, it does not detail how the 'values' array interacts with multiple selections, nor does it clarify the mutual exclusivity of 'ref' and 'selector'. Baseline 3 is appropriate.

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 clearly states the action ('Select') and resource ('option(s) of a <select>'), with the method ('by value or visible label'). It distinguishes this tool from siblings like click or fill_form by specifying the select element interaction, though it could be more explicit about HTML select elements.

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?

No guidance on when to use this tool versus alternatives like fill_form or click. The description does not mention prerequisites (e.g., element must be a <select>) or exclusions (e.g., not for radio buttons). Usage context is implied but not stated.

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