uncheck

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 states the core state-changing action but says nothing about side effects, error behavior, idempotence, whether change events are triggered, or what happens if the referenced element is not a checkbox.

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 a single clear sentence with no filler words. It is appropriately brief for a simple tool, though the lack of parameter explanation means brevity comes at the cost of completeness outside this dimension.

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 one-parameter action with no annotations and no output schema, the description should at least clarify what 'ref' refers to and note the relationship to similar tools. It does neither, leaving significant gaps for an agent trying to invoke it correctly in a real browsing context.

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 does not explain the meaning or expected format of the 'ref' parameter. The agent must guess whether ref is a selector, snapshot reference, DOM id, or some other identifier, so the description adds no value beyond the schema's bare string type.

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 states a clear action and target: 'Uncheck a checkbox.' It names a specific verb and resource, making the tool's purpose immediately understandable. However, it does not explicitly distinguish itself from the sibling 'check' tool or mention the role of the ref parameter, so it falls just short of full differentiation.

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 tool versus alternatives such as 'check', 'click', or 'fill'. The description implies usage only through the tool name and one-line purpose, with no context about prerequisites, selection criteria, or exclusions.

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