Wait locally for browser state

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), lowering the burden. The description adds that the wait is 'local' and scoped to URL/text/element conditions, but it does not disclose blocking duration, timeout outcome, or behavior when the condition is already satisfied.

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, front-loaded with the operational verb and a compact list of supported condition types. It contains no filler, though the brevity leaves little room for contextual 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?

The condition schema is complex, but the description only abstracts it into three kinds. Required target_id is unexplained, timeout and observe_after semantics are absent, and there is no failure or timeout behavior described; with no output schema, an agent would have to infer key runtime details.

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, but it only loosely maps to the condition parameter ('URL, text, or element'). It says nothing about target_id, timeout_ms, or observe_after, leaving key parameters unexplained.

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 identifies a specific action ('wait') on a resource ('browser state') and enumerates the condition families it supports: URL, text, and element. It does not explicitly contrast with siblings like observe or verify, but the verb and condition list make the core function reasonably distinct.

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 given about when to use wait_for versus alternatives such as observe or verify. There is no mention of scenarios like waiting after navigation, before assertions, or when a non-blocking check is preferred; usage is only implied by the tool's name.

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