check

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and target; it does not explain behavior for already-checked elements, disabled elements, whether the action dispatches native events, or whether it forces checking a radio button.

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?

The description is extremely concise and front-loaded, with no wasted words. It earns its place but is minimal to the point of omitting useful operational detail.

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 tool is simple, but the description leaves critical context undefined: what 'ref' accepts, whether it can be used on radio buttons and checkboxes both, and how it differs from 'uncheck'. Without annotations or an output schema, the description alone is not enough for reliable 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?

The sole required parameter 'ref' has 0% schema description coverage, and the description does not explain what 'ref' refers to. An agent cannot tell whether it is a selector, element ID, or snapshot reference from this definition alone.

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 clearly states the action ('Check') and the target resource ('checkbox or radio button'), so an agent can infer what the tool does. It is distinguishable from 'uncheck' by the opposite action, though it does not explicitly differentiate itself from generic 'click' or selection tools.

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?

Usage is implied by the verb: use this tool when you want to check a checkbox or radio button. However, there is no guidance about when to prefer this over 'click', 'click_role', or 'select_option', and no mention of prerequisites like element visibility or enabled state.

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