Wait for Browser Condition

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

Annotations already declare readOnly, idempotent, and non-destructive. Description adds that waiting observes live page/network but does not redact captured data, providing extra behavioral context beyond annotations.

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?

Extremely concise: two sentences plus preconditions and next steps. Every sentence adds value, no filler. Information is front-loaded and well-organized.

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 complexity (6 params, 1 enum) and existing annotations + output schema, description covers when, preconditions, next steps, and behavioral note. Lacks only some edge-case or error details, but overall sufficient.

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%. Description only mentions modes (selector, URL, quiet-period, timeout) and hints at narrow inputs. Does not explain parameters like delayMs, pattern, quietMs, timeoutMs, or their significance.

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?

Description clearly states the tool is for waiting for explicit browser conditions (selector, URL, quiet-period, timeout) instead of arbitrary sleep. Verb+resource is specific and distinguishes from other browser tools.

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?

Provides clear preconditions (active page required, narrow inputs) and next steps (perform action after condition). Implicitly contrasts with arbitrary sleep, but does not explicitly list alternative tools or conditions to avoid.

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