browser_is_checked

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

No annotations are provided, so the description must disclose behavioral details. It only states the action but does not explain return type (presumably boolean), error handling for missing selectors, or any side effects. This is a significant gap for a tool with no annotation support.

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 that is appropriately sized for a simple tool. It contains no fluff or repetition, making it highly concise and easy to parse.

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 simple tool with complete schema coverage, the description is minimally adequate. However, there is no output schema, so the description should at least mention that it returns a boolean or the checked state. The lack of return-value information leaves a completeness gap.

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 schema fully describes both parameters (selector and sessionId), so the description adds no extra meaning. Baseline 3 is appropriate because the schema carries the semantic load, and the description does not introduce conflicts or clarifications.

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 'Check if a checkbox/radio is checked' uses a specific verb and resource, clearly distinguishing it from sibling tools like browser_check (which sets the checkbox) and browser_uncheck. It precisely conveys the tool's query-like purpose.

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 intended use is implied by the name and description: to verify checkbox state. However, there is no explicit guidance on when to use this vs. alternatives (e.g., browser_is_visible or browser_is_enabled), nor any exclusions or prerequisites mentioned.

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