browser_select_option

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

With no annotations, the description must disclose behavioral traits. It fails to mention that selecting an option mutates the page state, does not address error conditions, or require element visibility. The description is insufficient.

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 very concise: a single sentence followed by a clear bullet-style parameter list. It is front-loaded with the core action, and every sentence is necessary.

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 description covers the basic action and parameters but omits important context like prerequisites (e.g., page snapshot must exist) and error scenarios. An output schema exists but its content is not shown, so the description could be more complete.

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 compensate. It provides brief but useful explanations for each parameter (e.g., 'Human-readable element description', 'Array of values to select'). However, details like value format or constraints are missing, making it adequate but not strong.

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 verb 'select' and resource 'option in a dropdown' are specific and clearly distinguish the tool from siblings like browser_click or browser_fill_form. The description immediately conveys the action and target.

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 for selecting dropdown options but does not explicitly state when not to use it or mention alternative tools. No guidance on prerequisites or edge cases is provided.

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