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

Annotations already indicate readOnlyHint=false, signaling this is a mutating operation. The description adds that selection can be by value or visible label, but does not disclose edge-case behaviors such as what happens if both are provided, which takes precedence, or what occurs if no matching option is found.

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 a single sentence that is direct and front-loaded with the verb 'Choose'. It wastes no words and conveys the core purpose efficiently.

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 or nested objects, the description covers the essential action and parameters. It lacks details on parameter precedence or error handling, but overall provides sufficient context for an agent to invoke it correctly.

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 compensate. It explains that 'label' and 'value' refer to the option's visible text and value attribute, respectively, but it does not clarify the 'selector' parameter's format or the precedence when both label and value are provided.

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 ('Choose an option') and the target resource ('<select> element'), and specifies the two methods ('by value or visible label'). This distinguishes it from sibling tools like 'click' and 'fill_form' in the context of browser automation.

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 selecting options in a dropdown, but does not explicitly state when to use this tool over alternatives like 'fill_form' or 'type_text'. There is no mention of exclusions or when-not-to-use, so the guidance is only implied.

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