select_option

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

With no annotations, the description carries the burden and does disclose real behavior: it sets the value and fires a change event, and submits=true triggers a permission request. It does not cover failure modes, index base, or what confirm/reason do, leaving gaps.

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?

Three tight sentences, front-loaded with the core purpose and the exclusivity rule. Efficient, with no filler, though the parenthetical about onchange is slightly wordy.

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?

An output schema exists so return values needn't be described, and the core behavior is covered. However, for a 7-parameter tool with 0% schema coverage, unexplained parameters (selector, reason, confirm) leave the definition short of 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?

Schema coverage is 0%, so the description must compensate. It explains the value/label/index exclusivity and submits, but says nothing about the required selector, reason, or confirm parameters, leaving several of the 7 parameters undocumented.

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?

States a specific verb ('Choose an option') on a specific resource ('<select>'), and explicitly distinguishes itself from the click sibling: 'A dropdown is not a click target.' An agent can route correctly without opening the schema.

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?

Gives a clear selection rule ('Give exactly one of the three' value/label/index) and the condition for submits=true (an onchange that posts). It also implies when not to use click. No explicit exclusions beyond that, so not a full 5.

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