Browser Wait For Timeout

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool waits for a fixed duration, but does not mention whether the wait blocks further actions, how timing errors are handled, or whether the session must be active. This is a significant gap for a tool that pauses execution.

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 concise sentence that is perfectly front-loaded. Every word earns its place, with zero redundancy or filler.

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 is minimal and fails to provide essential operational context for a tool that manipulates timing. It does not mention how it interacts with the browser session, potential side effects (e.g., blocking), or when this tool should be preferred over waiting for elements. With no annotations or output schema, this is inadequate for safe use.

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. While it mentions 'fixed number of milliseconds' which ties to the 'milliseconds' parameter, it provides no extra meaning for 'sessionId' or format constraints beyond the schema. The usage of the parameters is inferable but not explicitly clarified.

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 the core action ('wait a fixed number of milliseconds') with a specific verb and resource. However, it does not elaborate on what constitutes a valid session or any nuance about timing, so it is clear but minimal.

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 description gives no guidance on when to use this tool versus waiting for a selector (browser_wait_for_selector) or other alternatives. It only implies a fixed delay, leaving the agent to infer appropriate use cases.

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