browser_select

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Select dropdown option' reveals none of the tool's side effects, such as whether it triggers change events, waits for React updates, or requires visibility. It does not mention error conditions, return values, or any external effects. This is a severe gap for a tool that mutates UI state.

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 extremely short and front-loaded, which is concise, but it is under-specified. It conveys the core action and target without fluff, but the brevity leaves out critical context. It is not as vague as a single-word tautology, but it does not earn its place fully since it adds minimal value beyond the name and schema.

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 tool has no annotations, no output schema, and a simple but non-trivial action (selecting a dropdown option), the description is insufficiently complete. It fails to explain how to specify the option (by value/index/text), whether the dropdown must be open, or any expected behavior after selection. For an agent to invoke this reliably among 38 siblings, more context is needed.

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 schema includes descriptions for all three parameters (value, session, selector) with 100% coverage. The description adds no additional meaning beyond what the schema already states, so the baseline of 3 applies. No extra clarification is provided for how 'value' is interpreted (e.g., by attribute or text) or how '@ref' works.

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 'Select dropdown option' provides a clear verb ('select') and resource ('dropdown option'), which distinguishes it from generic click or fill tools. However, it lacks detail on what the selection entails (e.g., setting a value, triggering events) and does not explicitly differentiate from similar tools like browser_set, though 'dropdown' adds specificity. It is not a tautology but is minimal.

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?

There is no guidance on when to use this tool versus alternatives such as browser_click or browser_fill. The description does not state prerequisites (e.g., dropdown must be open) or scenarios where this is preferred. No context or exclusionary information is provided, leaving the agent to infer usage from the name and schema alone.

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