browser_select_option

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

No annotations are present, so the description must disclose behavioral traits. It only states the action without revealing whether selecting triggers events, waits for page updates, or requires the element to be focused. This leaves the agent uninformed about the tool's runtime side effects.

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, clear sentence that is not redundant or padded. However, it is under-specified, lacking any structured detail about parameters or use cases, which would be more informative than this terse statement.

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 tool has 3 parameters, no output schema, and no annotations. The description provides no context about expected inputs, return behavior, or interaction prerequisites, making it insufficient for an agent to use the tool correctly in a browser automation workflow.

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 0%, and the description does not explain the meaning or usage of 'ref', 'values', or 'element'. The agent must rely solely on parameter names and types, which is inadequate for constructing correctly formatted calls, especially for the 'ref' and 'element' properties.

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: selecting one or more dropdown values. It is specific about the action and resource, but does not differentiate it from other browser interaction tools such as browser_click or browser_type, which also manipulate page elements.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, such as having the dropdown element visible or the page fully loaded, nor does it reference related tools like browser_click or browser_fill_form.

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