Select option

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

The description is transparent about the side effects: it sets the value and fires input/change events, and the annotations confirm non-destructive, non-read-only behavior without contradiction.

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 short sentences, direct, and contains only relevant information with no filler or 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?

For a simple action tool with no output schema, the description provides sufficient context about the operation and its effects, though it does not describe the return value, which is not required here.

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?

Each parameter has a meaningful description in the schema; 'target' gets a concrete example format, 'values' explains the expected data, and 'element' is self-explanatory as a human-readable label.

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 one or more options'), the target element type ('<select>'), and distinguishes it from other browser interaction tools by focusing specifically on option selection.

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?

It explains how the action is performed ('One CDP call') and the resulting behavior ('sets the value and fires input/change'), which gives useful context, though it could more explicitly contrast with clicking or typing alternatives.

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