browser_select_option

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to repeat that selecting an option mutates state. It adds no additional behavioral context beyond the action itself—it does not mention side effects like triggering change events or altering form state, nor any permission requirements. Since annotations cover the safety profile, the minimal description is acceptable but not enriching.

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 extremely concise—a single sentence with no wasted words. It efficiently captures the core action. It is front-loaded with the action verb. However, it is so brief that it omits potentially useful context like the fact that it handles single and multiple selections (which is already in the schema) or any notes about dropdown behavior, but for pure conciseness it scores high.

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 schema covers all parameters and annotations indicate destructiveness, the description is minimally complete. However, it lacks contextual guidance on when to use this tool (e.g., after taking a snapshot to get the target reference), any prerequisites, or post-conditions. For a destructive action, an agent might need more info about what changes occur, but the existing structured data provides the safety flags, so this is acceptable but not thorough.

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?

All three parameters (target, values, element) are fully described in the input schema with clear meanings (target reference, array of values, permission description). The tool description adds no additional semantic detail beyond what the schema provides, so it meets the baseline but does not enhance understanding of parameter relationships or usage nuances.

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 states the specific action: 'Select an option in a dropdown' with a clear verb and resource. It is unambiguous about the tool's function and distinguishes it from sibling browser interaction tools (click, type, hover) that operate on different UI elements. However, it does not explicitly differentiate from other selection-like tools, but given the sibling list, no other tool handles dropdowns specifically, so it is clear enough.

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 versus alternatives, nor does it mention any prerequisites or exclusions. There is no indication of when a dropdown might require this tool instead of other interaction methods (e.g., clicking the dropdown and typing). An agent would have no context to decide between this and browser_click or browser_type in some scenarios.

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