browser_set_checked

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

No annotations are supplied, so the description carries the full transparency burden, but it discloses almost no behavior. It does not say whether events such as change/input are dispatched, what happens if the element is already in the requested state, whether setting checked=false on a radio button is a no-op or discards the group selection, or how errors are surfaced.

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?

A single front-loaded sentence with zero filler; every word contributes to identifying the resource and the types of widgets affected.

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?

The parameter surface is small and fully described by the schema, so the definition is close to callable. However, with no annotations and no output schema, the missing behavioral detail about event dispatch, radio semantics, and return value leaves real gaps for a multi-parameter mutation tool.

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 100%, so both the ref and selector targeting options and the checked default of true are already documented in the schema. The description adds nothing about precedence between ref and selector when both are given, or about the optional tabId. Baseline 3 applies.

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 description uses a specific verb ('Sets') with a specific resource and enumerates the affected widget types: checkbox, radio button, and switch toggle. An agent can immediately tell this mutates form-control state. It stops short of a 5 because it does not say how it differs from the nearby browser_click or browser_select_option siblings.

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 when-to-use guidance, no statement of when to prefer this over browser_click on a checkbox or over browser_select_option, and no prerequisites such as whether the element must be visible or in the current tab. The agent must infer the routing decision entirely from the tool name.

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