browser_wait_for_load

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the high-level wait action without covering important behavioral traits such as timeout handling, return values, error behavior, or what 'finished loading' means (e.g., network idle vs. DOMContentLoaded). This is insufficient for a tool that may block or fail.

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, direct sentence with no unnecessary words. It is front-loaded and efficient. While it is terse to the point of being under-specified, it is still well-structured for what it includes, so it earns a high score on conciseness alone.

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 tool's simplicity (one optional parameter, no output schema) and lack of annotations, the description still needed to explain when to use it relative to sibling wait tools and what it returns or throws on timeout. It does neither, leaving it incomplete for an agent to invoke confidently.

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 input schema already fully documents the single timeout parameter with a type, description, and default value (schema coverage 100%). The description adds no additional parameter semantics, so it meets the baseline expected when the schema handles 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 page to finish loading' clearly identifies the action (wait) and the target resource (page load), which is specific enough to convey the basic purpose. However, it does not distinguish it from sibling wait tools like browser_wait_for_navigation or browser_wait_for_url, so it misses full sibling differentiation.

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?

There is no guidance on when to use this tool versus alternatives. With several wait-related sibling tools (browser_wait_for_selector, browser_wait_for_navigation, browser_wait_for_timeout, etc.), the description provides no contextual cues or exclusions, leaving the agent without clear selection criteria.

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