下拉选择

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

No annotations are provided, so the description must disclose side effects. It does state that the tool modifies page form data, which is an important behavioral trait. However, it does not elaborate on other behaviors such as waiting for element availability, handling of multi-select, or failure conditions, leaving the transparency incomplete.

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 concise, consisting of two sentences that front-load the main function and follow with a permission note. Every sentence contributes purpose, with no redundancy or filler.

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 relatively simple tool with 100% schema coverage, the description covers the core action and side effect. It does not describe return values or more complex interaction patterns, but given the schema richness, it is adequately complete for an agent to select the tool 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?

The input schema provides 100% parameter coverage, so the description need not add detailed parameter semantics. The description mentions the choice between value and label, which duplicates schema information but adds no further clarity beyond what the schema already documents.

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 selects one or more options in a drop-down list (select), either by value or by visible label. This specific verb+resource structure distinguishes it from sibling tools like web_click and web_fill.

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 implicitly establishes when to use this tool—whenever interaction with a select element is needed—but it does not explicitly name alternatives or exclusion scenarios. Clear context for dropdown interaction is provided, though no 'when not to use' guidance is given.

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