browser_select_option

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

The description adds no behavioral context beyond the basic action, such as side effects, permission requirements, or handling of multiple values. Annotations already indicate destructive and open-world behavior, but the description itself fails to disclose any additional traits about how the dropdown selection is performed.

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 short sentence, with no redundant information. It is perfectly front-loaded and every word is purposeful, though it may be too brief to be fully helpful.

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 simplicity, the schema's thorough parameter descriptions, and annotations covering safety, the description is mostly complete. However, it omits any mention of how multiple values are handled on single-select dropdowns or how targets are acquired, which could be inferred from the schema but are not explicitly stated.

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?

The schema already provides full descriptions for all three parameters (target, values, element), achieving 100% coverage. The description offers no additional guidance or clarification about parameter formats, relationships, or edge cases, so it adds no value beyond the schema.

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 tool's function with a specific verb ('Select') and resource ('option in a dropdown'), distinguishing it from sibling browser interaction tools like browser_click or browser_type. It leaves no ambiguity about the tool's purpose.

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 provides no guidance on when to use this tool over alternatives, such as browser_type or browser_click, nor does it mention prerequisites like obtaining target references from a snapshot. There are no exclusions or contextual hints, leaving the agent to infer usage from the name and schema.

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