browser_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 disclosure burden. It clarifies that `visible=True` requires rendering, which is useful, but it does not disclose timeout behavior (whether failure throws or returns), polling behavior, or what happens if the element never 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 two tight sentences with no filler. The main action is front-loaded, and the `visible=True` clarification is placed where it adds immediate value without bloat.

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 simple wait operation, the description plus schema defaults is mostly sufficient to invoke the tool. However, with no output schema, no annotations, and no explanation of timeout or failure behavior, an agent cannot predict how the tool responds under negative conditions.

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 add parameter meaning. It explains `selector` and adds the rendered semantics for `visible`, but it omits `timeout` semantics such as units and default behavior, leaving an incomplete parameter picture.

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 uses a specific verb and resource: wait for an element matching `selector` to appear, with an explicit `visible=True` nuance. This distinguishes it from sibling tools like browser_wait and browser_wait_for_load by targeting element presence rather than page load or a generic delay.

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 when to use the tool: when waiting for an element to appear. However, it does not explicitly contrast this with browser_wait, browser_wait_for_load, or other alternatives, and offers no exclusions or conditions for preferring a different tool.

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