select_option

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

With no annotations, the description carries full burden but only states selection methods. It fails to disclose behaviors like waiting, error handling (e.g., if option not found), or implications for multi-select dropdowns. The timeout parameter suggests waiting, but this is not explained.

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?

Single sentence of 11 words, no redundancy. Front-loads core purpose and methods, making it highly efficient and well-structured.

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 tool with no output schema, the description covers the essential action and selection methods. It lacks details like whether it works with multi-select or clears current selection, but overall is sufficiently complete given low complexity.

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 low (50%) with by_text, by_value, by_index lacking descriptions. The description compensates by mentioning 'by visible text, value, or index', which clarifies the purpose of these undocumented parameters and indicates they are alternative selection strategies.

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 specifies 'Select an option from a <select> dropdown' with clear verb and resource, and distinguishes from sibling tools like click or type_text. It explicitly mentions the selection methods (visible text, value, or index), making the tool's purpose unambiguous.

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 <select> dropdowns but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or conditions for use. No 'when not to use' or alternative tool references are present.

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