wait_for_element

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

No annotations exist, so the description carries the full burden. It implies a blocking wait and optional state check, but says nothing about what occurs on timeout (error vs. empty return), the polling behavior, or that the call will block the caller for up to the timeout — the most important behavioral fact for an agent deciding to call this.

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?

Two compact sentences, front-loaded with the core behavior and followed by the situational hint. Nothing is padded or redundant, though the second sentence could be merged into the first for tighter structure.

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 5-parameter blocking tool with no annotations, no output schema, and 0% schema coverage, the description is too thin. An agent cannot determine timeout semantics, failure behavior, or the meaning of most parameters from this text alone.

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% across 5 parameters, so the description must compensate. It only hints at the selector fields ('matching element') and the state parameter; it never explains the units or default of 'timeout' (default 5, seconds vs. ms is ambiguous) nor what 'window_id' identifies, leaving most parameters undefined.

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 names a specific verb and resource ('Wait until a matching element exists') and adds the conditional-state aspect plus the async-UI-change scenario. It is clearly distinct from action siblings like click or type_text, though it never contrasts itself with find_elements, the immediate-return counterpart.

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?

'Useful after clicks that trigger async UI changes' gives a concrete trigger scenario, which is real usage guidance. However, it never states when not to use it (e.g., when the element is already present and find_elements would suffice) or names any alternative.

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