select

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

There are no annotations, and the description gives no behavioral details beyond the core action. It does not disclose whether the tool triggers change/input events, waits for options to load, clears previous selections, supports multiple values, or throws errors on invalid values. This ambiguity makes agent behavior unpredictable.

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, front-loaded sentence with no redundant words. While under-specified in other dimensions, the sentence itself is structurally efficient and easy to parse.

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 carries full responsibility for contextual completeness. It fails to explain return values, error handling, or usage edge cases (e.g., multi-select, dynamic options). An agent would lack critical information for reliable invocation.

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 fully covers all three parameters (selector, value, timeout) with concise descriptions, so the baseline is 3. The description adds no extra meaning beyond the schema, but the schema itself provides adequate parameter understanding.

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 the action ('Select option(s)') and the resource ('dropdown/select element'), making the primary purpose clear. It does not explicitly differentiate from siblings like fill or click, but the target element type is specific enough to avoid major confusion.

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?

No guidance is provided on when to use this tool versus alternatives such as fill or click. The description does not mention conditions like native select elements, multi-select requirements, or interactions with custom dropdown components, leaving the agent to infer usage.

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