wait_for_element

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 states the waiting behavior (poll until appears) but does not disclose what happens on timeout (error? return value?), polling interval, or whether it interacts with page loading. Since there is an output schema, the return behavior might be partially covered, but the description adds minimal behavioral context beyond 'wait until appears'.

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 short and front-loaded: it states the action and the criteria in a single sentence. No wasted words, but the timeout semantics are missing, which could be a single addendum.

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 2-parameter tool with an output schema, the description is minimally complete. It specifies the selector usage but leaves timeout behavior unaddressed. Since the tool name and description make the main purpose clear, an agent could likely call it correctly, but would need to infer timeout details. Given the complexity (browser automation) and the absence of annotations, a bit more detail would be expected.

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 explains the selector parameter implicitly ('matched by a CSS selector') but does not explain the timeout parameter. The timeout parameter's semantics (units, what happens when exceeded) are not described. The description adds some value for selector but not for timeout, which is a key parameter.

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 clear verb and resource: waiting until an element appears, identified by a CSS selector. It distinguishes from siblings like is_element_visible by focusing on appearance/waiting rather than visibility checking. Missing explicit title, but the description is sufficiently clear.

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 implies usage when an element is expected to appear after some action, but does not explicitly state when to use versus alternatives like is_element_visible or find_elements_count. No explicit when-not or alternative guidance. The agent must infer from context, which is adequate but not explicit.

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