wavexis_select_option

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

The description discloses side effects ('Changes the selected option, firing change and input events') and the return format (JSON with status/error keys), which complements the destructiveHint annotation, adding value beyond annotations.

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 at 3 sentences, front-loaded with the core action, and includes essential usage guidance and side effects without redundancy.

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 tool's complexity with a nested input schema, the description covers core functionality, side effects, and output format well. It misses explaining some parameters (backend, session_id) but the schema already covers them, making it largely 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?

With 0% schema description coverage, the description bears full burden but only hints at the 'value' parameter ('by value'). It does not explain other parameters like selector, backend, session_id, or wait_timeout, which are only documented 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 clearly states 'Select an option in a ``<select>`` element by value,' specifying the verb, resource, and method. It distinguishes between native `<select>` elements and alternatives like wavexis_fill or wavexis_click, which differentiates it from sibling tools.

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 explicitly advises when to use this tool (for native `<select>` elements) and when to use others (wavexis_fill for text inputs, wavexis_click for custom dropdowns), providing clear context and exclusions.

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