Wait

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only states the waiting action without revealing side effects, blocking behavior, session requirements, or return values. This is nearly tautological and provides no meaningful behavioral context.

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 directly states the action. It is not bloated or verbose, though it is underinformative. It earns a high score for conciseness due to its brevity, but it could be more structured with additional context.

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 absence of annotations, no output schema, and two required parameters, the description is too sparse to be complete. It lacks information about return behavior, whether the wait blocks the session, and how this wait relates to other browser operations. The tool is simple, but the description still leaves significant gaps.

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?

The schema has no descriptions for the two parameters, and the description adds minimal value by implying that timeoutMs is the number of milliseconds to wait. It does not explain sessionId at all, and with 0% schema coverage, the description should compensate more for the lack of parameter documentation.

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 'Wait for a number of milliseconds' clearly states the action and the unit of time, making the core purpose understandable. However, it does not differentiate this tool from sibling tools like browser.pause_for_human, which may also involve waiting, so it lacks sibling distinction.

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 provided on when to use this tool versus alternatives. There is no mention of use cases, prerequisites, or situations where this wait is preferred over other waiting mechanisms, leaving the agent without decision support.

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