browser_select_option

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

Annotations already flag destructiveHint=true and readOnlyHint=false, covering the mutation safety profile. The description adds no extra behavioral context beyond the verb 'select' – it does not mention that selection may trigger events, require the dropdown to be enabled, or that multiple values are handled through an array. Since annotations carry the safety information, the description adds minimal value here.

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, front-loaded sentence that immediately conveys the core action. It avoids any fluff or repetition, making it efficient for an agent to parse quickly. There is no 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?

For a simple dropdown-selection tool with a complete schema and no output schema, the description is largely sufficient. It correctly identifies the operation, though it could hint at how to obtain the target reference or that multiple values are accepted. These details are present in the schema, so the minor omission does not hinder correct invocation in most cases.

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 description coverage is 100%, as all three parameters (target, values, element) have descriptions. The description does not add further meaning about the parameters, such as how values map to labels or indices. With complete schema coverage, the baseline score of 3 is appropriate; the description adds nothing beyond what the schema already provides.

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 a specific verb (select) and resource (option in a dropdown), which clearly distinguishes it from sibling tools like browser_click or browser_fill_form. It unambiguously identifies the action without needing to inspect the schema.

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?

There is no explicit guidance on when to use this tool versus alternatives such as browser_fill_form or browser_type. The usage is implied from the name and schema, but the description does not mention prerequisites like needing a page snapshot or context for when dropdown selection is preferred over other input methods.

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