Set or clear the checked state of a checkbox or radio element via a selector. Use it to make form controls checked or unchecked during browser automation.
Set check (alias)
| Name | Required | Description | Default |
|---|---|---|---|
| checked | No | ||
| selector | Yes |
Changes observed during successful MCP inspections.
v4.3.0Does 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. It does not say whether the operation is idempotent, whether the target must exist, what happens if 'checked' is omitted, or whether it waits for the element.
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 not conciseness but under-specification. There is nothing to front-load because no substantive information is present.
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 two-parameter mutation tool with no annotations and no output schema, the description is completely inadequate; an agent has essentially no basis for correct invocation.
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% and the description adds no parameter meaning whatsoever. 'selector' (a CSS/selector string?) and 'checked' (the desired boolean state?) are both undocumented in schema and description.
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 phrase 'Set check (alias)' gestures at setting a checkbox-like state but never states the resource explicitly or what element it operates on. With siblings like check, checkbox, and toggle_checkbox, the agent cannot tell from the description how this differs from them, and '(alias)' only adds ambiguity about what it aliases.
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 when-to-use guidance, no conditions, no alternatives named. The agent gets no help choosing between set_checked, check, checkbox, and toggle_checkbox.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.