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 of behavioral disclosure, but it only says 'wait until an element is visible.' It does not mention timeout failure behavior, polling semantics, or that the condition can be clickable, present, or invisible. For a wait operation, these are important behavioral details.

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 a single, front-loaded sentence with no filler. It communicates the core operation efficiently and earns its place without unnecessary detail.

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?

Given four parameters, no annotations, and no output schema, the description is too thin. It omits the condition variants, timeout outcome, and any guidance on selection strategy or interaction with sibling tools, leaving important invocation details to inference.

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?

The schema already documents selector, by, and timeout with descriptions, covering 75% of parameters. The description adds a little semantic value by explaining the default visible condition, but it does not clarify the other condition enum values or how they affect waiting behavior.

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 clearly names a specific verb ('wait') and resource ('element'), and specifies the default condition ('visible on the page'). It is not a tautology and is understandable on its own, though it does not explicitly differentiate itself from siblings like wait_for_network_idle or is_displayed.

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?

No guidance is provided about when to use this tool versus alternatives such as wait_for_network_idle, find_element, is_displayed, or assert_element_visible. There are no stated exclusions, prerequisites, or routing hints, so the agent must infer usage from the name and schema alone.

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