safari_select_option

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

Describes that it sets .value and dispatches change event, and explains the scope limitation for selectors vs ref. No annotations provided, so description carries the burden; it covers key behaviors but omits return value and error handling.

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?

Two focused sentences plus a note about custom dropdowns. No redundant information; every sentence serves a purpose. Front-loaded with main action.

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?

Covers most relevant context: native vs custom, iframe support, and behavior. Missing return value or success indicator, but for a simple action tool this is acceptable. No output schema, so description should mention result.

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?

All three parameters have full schema coverage and the description adds context: explains the difference between selector and ref, and that value can be option value or visible label. This goes beyond the schema alone.

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?

Clearly states 'Select an option in a native <select> dropdown,' distinguishing it from custom dropdowns via sibling tools like safari_click. The verb 'select' and resource 'native <select>' are specific and 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?

Explicitly tells when to use this tool (native select) and when to use alternatives (safari_click for custom dropdowns). Also explains that ref is needed for iframes/shadow DOM, guiding the agent on correct usage.

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