wait_for_url

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

With no annotations, the description must disclose behavior but only states the basic waiting action. It omits critical details: timeout handling (e.g., error vs. return), polling interval, and whether the tool resolves on match or returns a result. The presence of an output schema suggests return values, but these are not hinted.

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 very short (one sentence), which is concise but at the expense of necessary detail. It could be expanded without losing conciseness by adding a brief note on pattern format or timeout default.

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 complexity of browser automation and the presence of many sibling tools, the description is incomplete. It lacks parameter semantics, usage context, and behavioral details, making it insufficient for an agent to use reliably without external knowledge.

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 parameters. It does not mention url_pattern or timeout at all, leaving the agent to infer usage from schema names alone. No format, constraints, or examples are provided.

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?

Description clearly states the tool waits for the URL to match a pattern, which conveys the primary purpose. However, it lacks specifics on what constitutes a pattern (e.g., regex, substring) and does not distinguish from siblings like wait_for_response, which waits for network responses.

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 on when to use this tool versus alternatives like wait_for, wait_for_download, or wait_for_response. The description does not mention prerequisites or contexts where this tool is preferred.

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