browser_select_combobox

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

With no annotations, the description fully discloses the multi-step behavior: opens the trigger, types value to filter, commits via keyboard, verifies the committed value, and falls back to clicking. It also explains the return format {committed, actual} + snapshot.

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 front-loaded with the purpose and gradually adds detail. It is slightly verbose but every sentence adds value, and the structure logically flows from intent to behavior to return. No wasted words.

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 no annotations, the description covers all necessary behavioral details, parameter meanings, and return format. It is complete for the tool's complexity and provides clear usage guidance, making it easy for an agent to select and invoke correctly.

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 0%, so the description compensates by explaining the `ref` parameter (the trigger) and `value` parameter (what to type). It also notes the `submit_key` default 'Enter'. However, it does not mention `session_id`, which is optional but could be clarified.

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 picks a value from custom/searchable dropdowns or comboboxes, specifically for country/country-code pickers and styled listboxes. It distinguishes itself from the sibling tool browser_select_option by mentioning that it handles cases where browser_select_option times out.

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 explicitly says to use this tool 'where browser_select_option times out,' providing a clear when-to-use scenario. It also gives specific guidance on filtering by country name rather than dial code, preventing common errors.

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