is_element_present

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It conveys that this is a read-only boolean existence check, which implies no mutation. However, it does not disclose whether the check is synchronous, whether it waits, or how it differs from wait_for_element_present and assert_element in terms of failure behavior.

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 one tightly worded sentence with no filler. The return value and condition are front-loaded, making it immediately scannable and appropriate for a simple predicate tool.

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?

An output schema exists to explain return values, but the description lacks selector syntax details and does not clarify whether the tool waits or immediately returns. For a simple existence check the core behavior is present, yet with no annotations a bit more context about its relationship to waiting and asserting tools would make it more complete.

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%. The description only repeats the generic notion of 'selector' without explaining the expected syntax (e.g., CSS, XPath), formatting, or how to target elements. This adds little meaning beyond the schema property name.

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 a specific operation: returning whether an element matching a selector exists in the DOM. The phrase 'exists in the DOM' semantically distinguishes this from visibility-based siblings like is_element_visible and waiting-based siblings like wait_for_element_present, though it does not explicitly name them.

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 explicit when-to-use or when-not-to-use guidance is provided. The wording implies this is for immediate presence checks rather than visibility, waiting, or assertion, but the description does not state exclusions or alternatives.

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