Browser Select Option

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

No annotations, so the description carries the full burden. It usefully discloses that it auto-detects Select2/jQuery and triggers the correct change events, which is real behavioral value. However it says nothing about failure modes (option not found), whether the select is synchronized/focused, or what is returned, leaving notable gaps for a mutation-style UI action.

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?

Front-loaded purpose, then a compatibility caveat, then compact runnable examples, then the alternative-tool escape hatch. Every sentence carries information; nothing is redundant.

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 5-parameter tool with only one required param and full schema coverage, the description covers the core routing and usage model well and no output schema needs explaining. Minor gap: it doesn't mention preconditions such as the page/dropdown being loaded or focus requirements.

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 100%, so the baseline is 3, but the two inline examples concretely demonstrate the value-vs-label distinction and show the selector pairing, adding practical meaning beyond the field descriptions. It does not explain mode/sessionId interaction, but those are documented in the schema.

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?

States a specific verb (select) and resource (option in a native HTML <select>) with the two supported addressing modes (value or visible label). It also distinguishes itself from sibling browser_click/type by clarifying the dropdown-specific scope.

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?

Explicitly names the fallback for unsupported cases: complex custom dropdowns that don't use <select> should go to browser_execute with jQuery. Also asserts compatibility with Select2/jQuery dropdowns, so the agent knows when this tool applies and when it does not.

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