browser_select_option

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

Discloses self-verification behavior, error handling (returns available labels on no-match), and return value (committed option + snapshot). No annotations provided, so description carries full burden, but it is fairly comprehensive.

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?

Concise, front-loaded with purpose, followed by conditions and return value, no unnecessary words.

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?

Covers main functionality, error handling, and return value. Output schema exists, so description needn't detail return structure. Could mention 'ref' format but overall complete.

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 0%, but description implies 'ref' is a locator and 'values' are options to select. It does not describe 'session_id' at all. Adds some value but not full parameter documentation.

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?

Description clearly states the tool selects options in a NATIVE <select> element by ref, matching by value or visible label. It distinguishes itself from sibling tools like browser_select_combobox for custom dropdowns.

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?

Explicitly says when to use (native <select>) and when not to (custom combobox), and directs to browser_select_combobox as an alternative.

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