browser_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 adds no behavioral details beyond the schema—no mention of return values, error handling, or the prerequisite of having a snapshot ref. The iframe guidance is already present in the schema, so it contributes no unique transparency.

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, front-loaded with the main action and no wasted words. Every sentence is purposeful, though the second sentence is somewhat redundant with the schema, it remains concise.

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 no annotations and no output schema, the description omits return value information and preconditions such as needing a snapshot ref. The core function is clear and schema covers all parameters, but the tool's complete behavior is under-specified for an agent to fully anticipate side effects or results.

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?

The input schema has 100% description coverage for all three parameters, so the description adds no new semantic information beyond what the schema already states. It merely reiterates 'by ref' and iframe usage, which the schema explains.

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?

Description clearly states 'Select option(s) in a dropdown by ref' with a specific verb and resource, differentiating it from other browser action tools like click or type. The iframe hint adds specificity, making it obvious what the tool does.

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?

Provides clear usage context with 'Use frameSelector when inside an iframe,' which indicates when to apply that parameter. However, it does not explicitly mention alternatives or when not to use this tool relative to sibling tools, 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.