sleeper_wait_url

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about how long it blocks, what happens on timeout (timeout_ms exists but is unexplained), whether it polls, or whether it throws vs returns a status. For a blocking wait tool this is a notable gap.

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?

A single front-loaded clause with zero filler, which is appropriately terse for the action. Brevity here reflects under-specification rather than wasted words, so it is efficient but not maximally informative.

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?

No annotations, no output schema, and three of four parameters undocumented, so the agent lacks timeout, return-value, and failure-mode context. A blocking wait tool needs more disclosure than one line.

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 coverage is only 25% — only profile is described in the schema. The description adds nothing about pattern (substring vs regex), tab, or timeout_ms defaults, so it fails to compensate for the coverage gap on a 4-parameter tool.

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?

States a specific verb (Wait) plus resource (URL) and the matching condition (contains pattern), which parses cleanly. It does not explicitly differentiate itself from sibling wait tools like sleeper_wait_text or sleeper_wait_until, so the agent must infer the distinction.

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 when-to-use guidance, no mention of when it fails or blocks, and no reference to alternatives such as sleeper_wait_until or sleeper_wait_text. Usage is only implied by the tool name.

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