wait_for_navigation

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 does not explain what 'page load complete' means (DOMContentLoaded, load event, network idle), what occurs on timeout, whether errors are thrown, or if it waits for frames/subresources. This is a critical gap for a blocking operation.

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 focused sentence with no filler, and the core purpose is front-loaded. It is concise, though perhaps too terse given the missing behavioral 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?

For a tool with no annotations, no output schema, and zero schema coverage, this description is insufficient. It omits timeout behavior, failure semantics, relationship to sibling wait tools, and what constitutes a completed page load. An agent cannot confidently invoke this tool correctly based on the current definition.

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 explain the timeout parameter, but it does not mention it at all. The agent is left to infer that the timeout parameter controls the maximum wait duration, which is not guaranteed and could be misused.

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 a clear verb ('wait') and resource ('page load'), and the phrase 'to complete' clarifies the condition being awaited. It is distinguishable at a high level from arbitrary wait_for, but it does not explicitly differentiate itself from navigation-specific siblings like wait_for_url, wait_for_response, or wait_for_network_idle.

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 provides no guidance on when to use this tool versus the many sibling wait tools. There is no mention of whether it should follow navigate, reload, or go_back, nor when to prefer wait_for_url or wait_for_network_idle.

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