select_dropdown

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only states the action itself and does not disclose whether the tool waits for interactability, fires change events, matches strictly, or what happens when no option matches or the select is not found.

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 one concise, front-loaded sentence with no redundant words. It efficiently communicates the core operation and selection modes without bloat.

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 is relatively simple and the schema covers all parameters, but because there is no annotations block or output schema, the description alone is only minimally sufficient. It lacks behavioral context such as waiting, matching semantics, failure behavior, and return value, making it adequate but not complete.

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 100%, so the schema already documents all parameters including defaults and enum values. The description adds little beyond restating the selection modes already present in selectBy and optionValue, so a baseline 3 is appropriate.

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 states a specific action and resource: selecting an option in an HTML <select> dropdown, and lists the supported selection modes (value, visible text, index). It is clear and distinct from generic sibling tools like click_element or fill_element, though it does not explicitly name alternatives.

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 does not provide when-to-use guidance, prerequisites, or exclusions relative to sibling tools. It implies the tool is for <select> dropdowns, but it never states that it should be used instead of click_element or fill_element for native selects, nor mentions custom dropdowns as a non-target.

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