ui_wait_for_element

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

With no annotations, the description must disclose behavioral traits. It only states deterministic synchronization and replacement of sleeps, but omits critical details: what happens if the element never appears (timeout, error?), how long it waits, whether it can be interrupted, and any side effects. This is insufficient for safe agent use.

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 very short and front-loaded, earning its place with no wasted words. However, it is a phrase rather than a sentence, and could be restructured as a complete sentence for clarity while remaining concise.

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 the tool's simplicity (no params, no output schema, no annotations), the description is the only source of information. It lacks coverage of error handling, timeout behavior, and how the tool determines which element to wait for (likely relying on prior context). This is insufficient for an agent to use it reliably alongside sibling UI tools.

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 input schema is empty (0 parameters) with 100% coverage, so the schema already conveys all parameter info. The description adds no parameter-specific details, but per guidelines a baseline of 4 is appropriate for zero parameters. No improvement needed, though noting context-dependence would help.

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 'Deterministic synchronization — replaces all sleeps' clearly indicates the tool is a smarter wait mechanism, and the name 'ui_wait_for_element' specifies it waits for a UI element. It conveys the purpose effectively but could more explicitly state it waits for an element to appear or become available.

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 this tool should be used instead of arbitrary sleep calls, but it provides no when-to-use vs. alternatives guidance. It does not compare with sibling tools like ui_find_element or other wait tools, nor does it mention prerequisites or when not to use it.

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