is_element_visible

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

No annotations are provided, so the description carries the full burden. It only states the core return behavior and does not clarify what 'visible' means (e.g., present in DOM, within viewport, not hidden via CSS), whether the tool waits or fails if no element matches, or how multiple matches are handled.

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 entire description is a single concise sentence with no redundant words. It is immediately readable and front-loads the action, making it easy for an agent 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?

Although the tool is simple, the description leaves out enough context that an agent could easily confuse it with is_element_present, is_text_visible, or wait_for_element_visible. It also lacks any behavioral nuance such as return-on-missing semantics, which matters for selection among siblings.

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 description coverage is 0%, and the description adds only the phrase 'matching the selector,' which confirms the selector identifies the element but does not explain expected format, syntax, or examples. For a single-parameter tool this is sparse but not catastrophic, hence a 2.

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 tool returns whether an element matching the selector is visible, with a specific verb ('return') and resource ('element matching the selector'). It does not explicitly differentiate from siblings like is_element_present or is_text_visible, but the distinction is largely inferable from the name and description.

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 wait_for_element_visible, assert_element_visible, or is_element_present. No context is given about typical scenarios, prerequisites, or why an agent would choose this over related checks.

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