browser_select_option

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

With no annotations, the description carries the full behavioral burden. It discloses the interaction sequence for custom dropdowns: clicks trigger, waits for options, then clicks matching option by text. This gives the agent a real sense of what the tool does beyond the schema. However, it does not describe the native <select> behavior or any side effects, leaving a small transparency 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?

The description is two sentences and every word earns its place. The core purpose is front-loaded, followed by the custom dropdown mechanics and the sibling tool alternative. There is no fluff, repetition, or unnecessary detail.

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?

The description is well-rounded for a UI interaction tool: it explains the two supported modes, gives the interaction flow, and routes to the correct sibling for autocomplete. With a fully described schema and no output schema expected, the only missing piece is explicit detail on how native <select> elements are handled, which is a minor omission.

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 100%, so the baseline is 3. The description adds value by explaining that the wait parameter is used after clicking the trigger for options to appear, and it reinforces that option is a partial-match text. This contextualizes parameters beyond the schema's individual descriptions, so a 4 is warranted.

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 opens with 'Select an option from a dropdown menu,' a specific verb and resource that immediately defines the tool's function. It also distinguishes this tool from browser_set_combobox by explicitly stating the autocomplete use case falls to that sibling. The scope is clear and not a tautology.

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 gives explicit usage guidance by covering native and custom dropdowns, and states 'For autocomplete (typing filters options) use browser_set_combobox instead.' This provides a clear when-to-use and when-not-to-use with a named alternative. It leaves no ambiguity about the intended scenario.

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