Uncheck a checkbox on a web page by providing its CSS selector. Enables agents to modify form state during browser automation.
Uncheck checkbox
| Name | Required | Description | Default |
|---|---|---|---|
| tab | No | ||
| profile | No | Browser ID from sleeper_sessions; optional with one connected browser. | |
| selector | Yes |
Changes observed during successful MCP inspections.
v2.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether it waits for actionability, what happens if the checkbox is already unchecked, error behavior for a missing selector, or whether it dispatches events. A mutation tool with zero behavioral disclosure.
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?
Three words is under-specification rather than conciseness; there is no structure, no front-loaded scope, and no sentence that informs invocation beyond the name itself.
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?
With no annotations, no output schema, a required undocumented parameter, and no mention of sibling tools for checking vs unchecking, the definition is not complete enough to call this tool confidently in a 49-tool browser-automation set.
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 33% (only 'profile' is documented). The description adds no meaning for 'selector' (required) or 'tab' — it does not say whether selector is CSS, XPath, text, or an element handle, nor that the field must be a checkbox.
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?
States a concrete verb+resource ("Uncheck checkbox"), which is enough to know the operation, but it does not distinguish itself from the sibling sleeper_check or explain how it differs from a click on a checkbox. Minimal but not tautological.
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?
No guidance whatsoever on when to use this instead of sleeper_check, sleeper_click, or sleeper_select. The agent must infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.