select_option

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

The annotations already disclose that this is a mutating operation (readOnlyHint=false) but not destructive, with open-world behavior. The description adds that selection targets a <select> and can use either a value or visible label, but it does not explain edge cases such as invalid options, change-event triggering, or whether the selector must target a select element.

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 wasted words and no redundant restatement of the name or schema.

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 output schema means return values need not be explained, and annotations cover safety characteristics. However, for a mutation tool with zero schema descriptions, the definition leaves selector semantics and important interaction behavior (such as whether change events fire or what happens on a missing option) unspecified.

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 description coverage is 0%, so the description must carry parameter meaning. It usefully clarifies that 'value' can be either the underlying value or the visible label, but it leaves 'selector' unexplained beyond the common term, so compensation is only partial.

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 a specific verb and resource: 'Select an option in a <select>'. It is clear what the tool does and distinguishes itself from generic sibling actions like click or type_text, though it does not explicitly call out those alternatives.

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 phrase 'by value or visible label' implies how the tool is used, but there is no explicit guidance on when to prefer this over click, fill_form, or type_text, nor any exclusions or prerequisites.

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