wait_for_url

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

With no annotations provided, the description carries the full behavioral burden and does well: it discloses blocking semantics, URL matching mode (regex or plain substring), readyState gating via wait_ready, return values, and in-page polling. The only notable omission is how timeout behaves when the pattern is never matched.

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 compact, front-loaded with the core behavior, and every sentence earns its place: the core wait condition, the return values, the usage context, the contrast with wait_for, and the polling cost note. There is no 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?

Given the moderate complexity and presence of an output schema, the description adequately covers when to use the tool, what it waits for, and what it returns. The main gap is the absence of timeout failure behavior, which matters for an agent deciding how long to wait or how to handle errors.

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. It usefully explains url_pattern (regex or plain substring) and wait_ready behavior, but it does not clarify timeout units or timeout failure behavior, nor does it mention session_id. Since two of four parameters remain semantically underexplained, this is only partial compensation.

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 clearly states a specific action ('Wait for navigation to settle') and resource (the tab's URL and readyState). It also distinguishes itself from the sibling wait_for tool by describing exactly what wait_for does not do, so an agent can tell them apart immediately.

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?

It explicitly says when to use this tool ('after a click or open_url that navigates') and names the alternative wait_for, explaining why wait_for is insufficient. This gives an agent a concrete decision rule with no inference required.

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