Check page control

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

The description adds behavioral details beyond annotations: it explicitly states idempotency, timeout bound (timeoutMs), and session isolation. It also clarifies the locator strategy (semantic or CSS). No contradictions with annotations.

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?

Two concise sentences with no excessive detail. The description is well-structured and directly conveys the essential information.

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 description covers the main action and key constraints (idempotent, timeout, session). It does not delve into edge cases like element not found, but since an output schema exists (though not shown), return values are not required. Overall, it is sufficiently complete for typical use.

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 only mentions timeoutMs and session indirectly. It does not explain the meaning of ref, pageId, or locator structure. Given the schema has 5 parameters with 0% description coverage, the description adds limited parameter meaning.

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 (ensure a checkbox or radio is checked) and specifies the target type and how it is located (semantically or by CSS). It also distinguishes from similar tools like uncheck by focusing on checking.

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?

The description implies usage for checking checkbox/radio elements and mentions authentication via session, but it does not explicitly contrast with alternatives like browser_click or browser_uncheck. However, the purpose is clear enough to infer when to use it.

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