Select Dropdown Option

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

The description discloses error handling behavior (Playwright throws for invalid selector or option) and the return structure with selected values. These go beyond the annotations, which only indicate mutability and destructiveness hints, providing useful context for the agent.

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 well-organized with clear sections for args, return value, examples, and error handling. Each sentence adds value, and the overall structure is easy to scan.

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 the 8 parameters and output schema, the description covers the core selection behavior, tab targeting, return value, and error scenarios. It could be more explicit about the mutual exclusivity of tab targeting parameters, but the schema and description together provide sufficient context.

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 schema descriptions (100% coverage), so baseline is 3. The description adds crucial mutual-exclusivity information for value/label/index and clarifies the optional tab selection parameters, which is not fully captured in the schema.

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 uses the specific verb 'Chooses' and identifies the resource as 'a native <select> dropdown', and clarifies selection by value, label, or index. This clearly distinguishes the tool from siblings like operagx_click or operagx_type_text.

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 provides an explicit use case in the example ('choose \'Option 2\' from the dropdown') and specifies that exactly one of value/label/index must be used. It implicitly limits usage to native <select> elements, setting boundaries relative to custom dropdowns, but does not explicitly state when not to use it.

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