Select option

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

No annotations are provided, so the description carries the full burden. It only says 'select options', not disclosing side effects (e.g., page mutation), requirements (element must be <select>), or limitations (only single selections? multiple?). This is insufficient for a UI interaction tool.

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 sentence with no wasted words. It is front-loaded with the core action and resource.

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?

With no output schema, no annotations, and only partial parameter coverage, the description fails to provide sufficient context. It doesn't explain what happens after selection (e.g., page update, event triggers) or error conditions. For a UI interaction tool, this is inadequate.

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 75%, and the description adds context for the ref parameter (source). However, the values parameter lacks description in both schema and description, and the description does not explain the relationship between parameters or usage patterns beyond ref.

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 tool selects options in a <select> element using a ref from browser_snapshot. It uses a specific verb and resource, and distinguishes from sibling tools like browser_click or browser_fill_form.

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 implies usage after browser_snapshot by mentioning 'by ref from browser_snapshot', but gives no when-to-use or when-not-to-use guidance, nor any alternatives.

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