browser_wait_for

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

With no annotations, the description must fully disclose behavior. It lacks details on whether the wait is blocking, polling behavior, timeout duration, or what happens if conditions are not met. The return value is vaguely described as a 'success message', leaving behavioral uncertainty.

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 extremely concise: one sentence covers all three wait modes, followed by a minimal arg list. Every sentence serves a purpose with zero filler, and key information is front-loaded.

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?

The description covers the core functionality but omits important context such as default behavior when no parameters are provided, error handling, or relationship to other browser tools. Since an output schema exists, return values are not needed here, but missing timeout details and parameter interactions reduce completeness.

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 description explains each parameter's role (text to appear, text_gone to disappear, time in seconds), which adds meaning beyond the schema's type-only definitions. However, it does not clarify constraints like mutual exclusivity among parameters or format requirements.

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 states that the tool waits for text to appear, disappear, or for a specified time. It uses a specific verb ('wait') and identifies the resource ('text', 'time'), distinguishing it from sibling tools like browser_click or browser_navigate.

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 on when to use this tool versus alternatives. It does not mention preconditions, when not to use it, or that it might be used after actions like navigation or clicks. The implicit usage is clear but not elaborated.

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