await_url

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

The description discloses key behavioral traits: blocking execution until condition or timeout, and optional body content checking. It also notes the agent is 'stuck' during the wait, which aligns with the blocking nature. Missing details about failure modes (e.g., unreachable URL) and polling interval behavior, but the schema covers interval.

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 two terse sentences plus an illustrative example. It front-loads the core behavior without wordiness, and every sentence contributes meaning.

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 no annotations and no output schema, the description covers the essential behaviors (blocking, timeout, body check) but omits what happens on timeout (e.g., error/return value) and does not reference sibling tools. It is mostly complete but leaves minor gaps.

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 100% for all five parameters, so the baseline is 3. The description adds an example but does not explain parameters beyond what the schema already provides.

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 the tool's action (block agent execution), the resource (URL), and the specific condition (expected HTTP status code, optional body string). This distinguishes it from sibling await tools that target commands and files.

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 context for using this tool is clear: wait for a URL to return a specific status. The example further illustrates a health-check scenario. However, it does not explicitly mention alternatives, exclusions, or when to prefer this over await_command/await_file.

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