select_from_combobox

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

No annotations exist, so the description carries the full load — and it does: it discloses that the container is opened and the popup closed again, that virtualized entries not yet in the tree are still matched, that matching is exact/case-sensitive, and the precise failure mode ('no such element', with a recommended recovery via expand_element + get_page_source). That is far more than 'select' implies.

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?

Four front-loaded sentences with no filler; the recommendation and the target-element clarification appear before the failure/recovery detail. It is dense, but every sentence carries actionable information rather than restating the name.

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?

With no annotations and no output schema, the description covers everything an agent needs: the target element, the matching rule, the side effects on the popup, the failure signature, and the recovery path. Nothing material is left to inference.

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 baseline is 3, but the description adds real meaning beyond the schema: 'Pass the combo box itself, not an item inside it' disambiguates the elementId target, and the exact/case-sensitive matching semantics for `value` are reinforced in prose.

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+resource+scope ('select an entry by its text from a combo box / dropdown (or any list box or tree) in one call'), with a concrete one-call contrast to the multi-step alternative. An agent can distinguish it from select_item/expand_element without opening any 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 says 'Prefer this over expand_element + find_element + select_item/click_element whenever you know the text', and names two exclusion cases (dropdown as separate top-level window, editable combo boxes for free text -> use set_element_value). When/when-not/alternatives are all present.

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