wait_for_url

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not explain what happens on timeout, whether an error is thrown or a boolean is returned, whether it polls repeatedly, or how it relates to the current page navigation. The behavior is only minimally implied by 'Wait'.

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 short and front-loaded, but it is under-specified rather than appropriately concise. It earns its place as a sentence, yet it omits behavioral and usage details that would make the tool safe to invoke without further inference.

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 lack of annotations, no output schema, and a partially described schema, the description is not complete enough. An agent cannot tell what happens on failure, how timeout works, or how this tool differs from the many related wait/assert tools in the sibling list.

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 provides descriptions for only one of two parameters (50% coverage), and the description adds no additional meaning beyond the term 'pattern'. The timeout parameter and its behavior are left undocumented in both the description and the schema, so the description does not compensate for the coverage gap.

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 ('URL to match a pattern'), so an agent can understand the basic operation. It is not a tautology and is distinguishable from siblings like wait_for_response or wait_for_request, though it does not explicitly name those alternatives.

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 about when to use this tool versus alternatives such as assert_url_matches, wait_for_response, or wait_for_request. The description only states what it does, not the conditions under which it should be chosen or avoided.

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