Choose a dropdown option

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

No annotations, so the description carries the burden. It adds real context (matches by visible text, works on native and custom widgets, sibling routing for checkboxes), but omits failure behavior, whether a custom combobox must be opened/expanded first, viewport auto-scroll, and what happens when option text is ambiguous or absent.

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?

Three short sentences, zero filler, with the core action front-loaded before the disambiguation rules. Every sentence earns its place.

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 two-parameter tool with full schema coverage and no output schema, the description covers purpose, routing, and widget scope adequately. Only edge-case behavior (not-found option, collapsed custom menu) is absent, which is a minor gap at this complexity.

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 coverage is 100%, so both params are already documented ('Option text', 'Dropdown id from browser_elements'). The description's 'by its visible text' and 'dropdown' wording only lightly reinforces what the schema states; no added semantics such as matching rules or format expectations.

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?

States a specific verb (pick) and resource (option in a dropdown) and explicitly covers both native <select> and custom combobox/menu variants. An agent can distinguish it from browser_click and browser_fill without opening 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?

Explicitly routes: use this instead of browser_click for dropdowns, and use browser_click for toggles/switches/checkboxes, with a pointer to browser_elements for their state. Both the when-to-use and the alternatives are named.

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