uncheck

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

The description provides minimal behavioral insight. It does not disclose side effects, error handling, or prerequisites. Without annotations, the description should offer more context about what happens when the tool executes.

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?

While the description is very short, it sacrifices completeness. It does not earn its place as it provides only the bare minimum, leaving critical gaps in understanding.

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?

Given the complexity of UI automation and the large sibling set, the description is too sparse. It fails to convey important details such as what 'untick' means in practical terms, return values, or error conditions.

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 description contains no parameter information. Schema coverage is 0%, and parameter titles 'Ref' and 'Selector' are vague. The agent is left guessing how to use these fields to locate the 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?

The description states the action (untick) and target (checkbox) clearly. However, it lacks differentiation from sibling tools like 'check' and doesn't specify the context (e.g., web UI), which could lead to ambiguity in tool selection.

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 is provided on when to use this tool vs alternatives. The sibling list includes 'check' and many other UI interaction tools, but the description offers no situational advice or exclusions.

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