wait_for_element_absent

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

With no annotations, the description carries the full behavioral burden. It discloses the default timeout behavior ('If no timeout given (0 or None), then SeleniumBase uses 7 seconds') and the failure outcome ('Raises an exception if the element is still present after the timeout'), making the tool's behavior transparent.

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 three short, front-loaded sentences. The purpose is stated first, followed by the timeout default and then the exception behavior. Every sentence carries useful information with no redundancy.

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 is complete enough for a simple two-parameter wait operation: it specifies what to wait for, the default timeout, and the failure behavior. Since an output schema exists, return values need no explanation. A slight gap is the lack of guidance about how selector syntax works, though this is likely shared across sibling tools.

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. It adds meaningful semantics for the timeout parameter by explaining the default value and effect, but it gives no additional guidance about the selector parameter beyond calling it a selector. This is partially sufficient but not fully comprehensive.

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 action with a clear condition: 'Wait until an element is removed from the DOM.' This distinguishes it from sibling tools like wait_for_element_visible and wait_for_element_not_visible by emphasizing removal from the DOM rather than visibility.

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 clearly communicates the tool's intended purpose: waiting for DOM removal rather than mere invisibility. It does not explicitly name alternatives or say when not to use it, but the 'removed from DOM' wording gives adequate contextual differentiation from the sibling wait tools.

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