sleeper_wait_until

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

With no annotations, the description carries the full behavioral burden. It discloses one important constraint—Chromium-only JavaScript predicates—but says nothing about timeout behavior, default interval, whether existing satisfied conditions return immediately, or what happens on timeout.

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 sentence with no waste, but for a 6-parameter wait tool with no annotations and no output schema, it is severely under-specified. Brevity here is not appropriate sizing; it leaves critical details unstated.

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 complexity—six optional parameters, a nested condition object, no output schema, and no annotations—the description is incomplete. It lacks timeout/interval semantics, profile/tab context, and condition-field guidance, though it does note the Chromium-only predicate limitation.

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 50%, so the description should compensate. It only alludes to condition and predicate; it adds no meaning for tab, profile, timeout, or interval, and does not explain the nested condition fields beyond what the schema already partially covers.

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 states a specific verb and resource: 'Wait for a structured page condition.' It distinguishes the tool from simple text/URL waits by focusing on structured conditions and predicates, but it does not explicitly name or differentiate from siblings like sleeper_wait_text or sleeper_wait_url.

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 only usage guidance is the constraint that JavaScript predicates are Chromium-only. It does not say when to choose this tool over alternatives such as sleeper_wait, sleeper_wait_text, or sleeper_wait_url, nor does it describe prerequisites or exclusions.

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