browser_check

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

With no annotations, the description carries the full behavioral burden for a mutation tool, yet it discloses nothing beyond the action itself: no scroll-into-view, event dispatch, error-on-missing-element, or idempotency behavior, and no return info. The only implicit hint is that a boolean 'checked' can both check and uncheck.

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 no wasted words. It is efficient, though brevity here tips into under-specification rather than crisp conciseness.

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 3-param mutation tool with no annotations, no output schema, and 0% schema coverage, the description is far too thin. Key details like tab targeting, selector syntax, and failure behavior are absent.

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%, so the description must compensate, but it only loosely maps to 'checked'. Neither 'selector' (format expected) nor 'tab_id' (which tab is targeted) is explained anywhere.

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?

Specific verb 'Set' plus a precise resource ('checkbox or radio's checked state') makes the action unambiguous and separates it from browser_click/browser_fill in concept. It stops short of naming alternatives or noting that it targets form controls specifically, so it isn't fully sibling-differentiating.

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 mention of alternatives such as browser_click, browser_select_option, or browser_fill, and no prerequisites (e.g., that the element must be a checkbox/radio). The agent is left to infer usage entirely.

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