wait

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

With no annotations, description carries full burden. It discloses that element waiting 'polls until visible' and that seconds creates a delay. However, it omits behavior for missing elements (timeout), error handling, side effects, and whether both parameters can be used together. The constraint 'browser driver only' is useful.

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?

Single sentence that front-loads the core purpose ('wait for element or delay') and appends the essential constraint. No extraneous information.

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?

Tool is simple with 4 parameters and no output schema. Description covers two main modes but lacks details on timeout behavior, mutual exclusivity of seconds and description, and return value. Adequate but not comprehensive.

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 coverage is 100%, with each parameter already described. The description adds minimal value: it re-emphasizes the delay semantics for 'seconds' and specifies polling for 'description'. Baseline 3 is appropriate given high schema coverage.

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 verb 'wait' and the two possible targets: 'element' or 'delay', with a specific constraint 'browser driver only'. This distinguishes it from sibling tools like click or goto, which perform different actions.

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?

Description implies usage for waiting, but provides no explicit guidance on when to use wait versus sibling tools (e.g., when to use poll vs delay, or when network waits are needed). No alternatives or exclusions are mentioned.

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