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. It only states 'Returns: JSON response from the API' with no mention of side effects, required page state, permissions, or error behavior. For a mutation-like action on a dropdown, this is minimal.

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 efficient: one line for purpose, then a clear Args list, then Returns. It is front-loaded with the action and wastes no words.

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 simple select action, the description covers the parameters and return type. However, it lacks any preconditions (e.g., page must be loaded), error scenarios, or interaction with waiting behavior. Given an output schema exists (per context signals), return format is presumably defined there, so the main gap is usage context and 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 description coverage is 0%, so the description must explain parameters. It does: serialno is identified as from list_devices, selector is a CSS selector for the select element, and value is the option value to select. This adds meaning beyond the bare schema titles, though the meaning of 'value' could be ambiguous (visible text vs. value attribute).

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 action 'Pick an option in a dropdown' and the selector parameter clarifies it targets a 'select element', distinguishing it from sibling tools like browser_click or browser_fill. However, it does not explicitly name alternatives or contrast with them.

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 other browser interaction tools such as browser_click or browser_fill. The description only states what it does, not when it is the appropriate choice.

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