browser_select

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 states it returns an updated snapshot but does not disclose behavioral traits like whether it triggers events, requires specific page states, or is destructive. The mutation aspect is implied but not explicit.

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 short and well-structured with a lead sentence followed by a bulleted list of arguments. It avoids unnecessary details, making it efficient, though it could be slightly more concise by integrating the list into the main sentence.

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 existence of an output schema, mentioning the updated snapshot is sufficient. However, the description lacks information on error handling, prerequisites (e.g., element must be a <select>), and behavior on no match. The tool has 3 optional parameters, and the description covers their usage but not edge cases.

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 0%, so the description must compensate. It explains value, label, and index well (e.g., 'Option value attribute to select'). However, required parameters page_id and ref are only named, not described beyond their names, which are self-explanatory but lack full context.

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 a dropdown option by ref ID, using a specific verb and resource. It distinguishes itself from sibling tools like browser_click or browser_type by focusing on select elements and requiring value, label, or index.

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 specifies to provide one of value, label, or index, giving clear selection criteria. It does not explicitly mention when not to use or alternatives, but the context of sibling tools implies this is for dropdowns only, which is adequate.

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