browser_wait_for_element

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: it returns immediately on success rather than sleeping a fixed duration, and it polls at an interval. It does not state what happens when the timeout elapses (error vs. empty/false return), which is the one behavioral detail an agent most needs for a wait tool.

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?

Front-loaded one-line purpose followed by the alternative-to-sleep rationale, then a tidy Args block. Efficient, with only slight redundancy in repeating schema defaults.

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?

No output schema and no annotations, so the description must stand alone; it covers purpose, mechanism, and every parameter. The missing piece is timeout-failure semantics and confirmation of the return value (found element vs. boolean), a notable gap for a waiting tool.

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, and it documents all four parameters with units and examples ('#results', '[data-loaded]', '10000 = 10s', '200ms'), plus the optional/defaulted tab_id. This is richer than the bare schema.

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?

States a specific verb ('wait for') and resource (CSS selector becoming visible), which clearly separates it from non-wait siblings like browser_screenshot or browser_click. It does not explicitly distinguish itself from the other browser_wait_for_* siblings (url, title, network_idle, result), so it stops short of a 5.

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?

Gives a clear condition for use ('waiting for dynamic/JS-rendered content') and names an alternative to avoid ('use this instead of sleep'). No explicit when-not guidance or routing to the sibling wait tools (wait_for_url, wait_for_title), so it is clear context rather than full decision guidance.

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