selectOption

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

No annotations are present, so the description carries full burden. It discloses the selection mechanism (value/text/index) but adds minimal behavioral context beyond the schema. It does not mention side effects, prerequisites like element visibility, error behavior, or whether the operation modifies the page state. This is a significant gap for a mutation-like action.

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 two sentences, concise and front-loaded with the main action. It avoids unnecessary detail and every sentence carries meaning.

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 simplicity, the description covers the core purpose and selection alternatives. However, it omits behavioral details like what happens when multiple selection criteria conflict, whether the select must be visible, or any prerequisites. With no annotations or output schema, a bit more context would be helpful, but it is not severely incomplete.

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 100%, so the baseline is 3. The description's phrase 'Specify value, text, or index' echoes the schema but adds no new semantic meaning. The priority ordering is already in the schema descriptions, so the description does not enhance 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 clearly states the action 'Select dropdown option' and specifies the two ways to identify the element ('by APOM ID or CSS selector'). This distinguishes it from sibling tools like click or type, and is a specific verb+resource combination.

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 indicates the intended use by telling how to select (by APOM ID or CSS selector, specifying value/text/index). It provides clear context but does not explicitly mention when not to use this tool or compare with similar alternatives like selectFromGroup, so it falls short of a 5.

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