browser_select

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

No annotations are provided, so the description carries the burden. It states the action but does not detail side effects such as whether change events are triggered, if prior selections are cleared, or behavior when no matching option is found. This is a moderate gap.

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 concise sentence that effectively conveys the core purpose without 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?

The description and schema fully cover the parameters and action. It omits edge cases like multiple matches or error handling, but for a simple select operation, it is reasonably complete. No output schema exists, so no return value explanation is needed.

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 parameters have descriptions (schema coverage 100%), and the descriptions clarify their roles. However, they do not explain the mutual exclusivity or priority (value over label over index), which is important for correct usage. This adds some meaning but not full clarity.

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 action (select an option) and the target resource (a dropdown `<select>` element). It is distinct from sibling tools like `browser_click` or `browser_fill` which handle other interactions.

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 implies use for dropdown selection, and there is no alternative select-specific tool among siblings, so it is the obvious choice. However, it does not explicitly mention when not to use it (e.g., for non-select elements), but this is implied by the resource mention.

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