选择下拉选项

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

readOnlyHint is false, consistent with the description's 'real click' indicating a mutating action. The description transparently states it performs clicks but does not mention potential side effects or failure modes, which is acceptable for a simple UI interaction tool.

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 a single, concise sentence that efficiently communicates the tool's purpose and the key action without unnecessary verbosity.

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 straightforward and the description covers the essential behavior. While no output schema is shown, this is common for UI interaction tools that return a success indicator, and the description does not need to elaborate further.

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 covers all five parameters with clear descriptions, including the match type (exact) and timeout. The description does not add extra meaning beyond the schema, but the schema itself is self-explanatory and detailed.

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 operates an AntD dropdown by clicking to expand and selecting a matching option. It distinguishes itself from sibling tools like antd_get_options and antd_date_pick by focusing on the selection action.

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 explains the interaction steps (real click to expand, click matching option in portal overlay) but does not explicitly contrast with alternative tools like element_select or antd_get_options. However, the context is clear enough for the intended use case.

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