sleeper_select

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

With no annotations, the description carries the full behavioral burden. It does disclose one meaningful trait — that it triggers a change event, which matters for sites reacting to input events — but says nothing about whether it waits for the element, what happens on failure, or what it returns.

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?

It is a single compact phrase with no waste and the action is front-loaded, but the brevity tips into under-specification rather than disciplined conciseness.

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?

No annotations, no output schema, and 25% parameter coverage leave the description doing very little for a 4-parameter browser-automation tool. An agent has no way to confirm selector format, session requirements, or error behavior from this definition alone.

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 only 25% (only 'profile' is documented, as the browser ID from sleeper_sessions). The description adds no meaning for selector, value, or tab, leaving three of four parameters undocumented in both places for a tool whose correctness hinges on how the selector is expressed.

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?

"Set select value + change event" names a verb (set) and a target (select value), implying it assigns a value to a <select> element and dispatches a change event. That is more specific than a tautology, but it never clarifies what a "select" is (HTML dropdown vs. a selection of elements) or how it differs from the many sibling interaction tools like sleeper_type, sleeper_click, or sleeper_fill_form.

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 instead of alternatives such as sleeper_fill_form, sleeper_type, sleeper_check, or a generic click-and-pick flow. An agent gets no signal about prerequisites (e.g., a connected browser session) or when this tool is the wrong choice.

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