safari_react_select_set

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

No annotations provided, so description carries full burden. It discloses that it bypasses the menu UI and invokes onChange directly, returns JSON with success/failure and up to 30 option labels on miss, and explains matching criteria. Lacks mention of any side effects beyond the direct action, but that's acceptable for a set operation.

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?

Description is slightly long but well-structured. First sentence gives core purpose, then usage, then return format, then matching, then requirements, then a NOTE. Front-loaded and easy to scan. Could trim some repetitive details, but overall efficient.

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's complexity (React fiber, specific frame-level workaround), the description covers everything: what it does, when to use it, return format, matching rules, required arguments, and a dependency ordering note. No output schema exists, but return values are fully described. Differentiates from siblings well.

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 has 100% description coverage. Description adds context: ref is 'Ref ID from safari_snapshot', selector is 'CSS selector — typically input[name=...] or the .react-select__control container', value is 'Option label (or value) to select — case-insensitive fallback'. Also clarifies that 'Either ref or selector required' even though schema lists them as optional.

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?

Description clearly states the tool sets a value in a react-select v5 dropdown by walking React fiber and invoking onChange directly. It specifies the exact resource (react-select v5 dropdown) and the unusual bypass mechanism, differentiating it from sibling tools like safari_click and safari_select_option.

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: 'Use when safari_click on the chevron or option keeps failing' with examples like Cloudflare forms and portal-rendered selects. Also provides a critical ordering note for dependent selects (set Permissions first). No guesswork needed.

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