Wait for download

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

With no annotations, the description carries the full behavioral burden. It does disclose useful traits: it targets the *most recently started* download, blocks only until completion, and returns the saved path in the user's Chrome download folder. However, it omits what happens on timeout (the schema's 120s default) or on download failure, which are the key risks for a wait-style tool.

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?

Three short sentences, front-loaded with the core behavior, and "Returns as soon as it finishes" usefully clarifies that it does not block for the full timeout. 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?

There is no output schema, so the description correctly fills that gap by naming the return value (saved file path) and its location. It is nearly complete for a simple wait tool, missing only failure/timeout outcome behavior.

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%, so slot, agent, and timeout are already fully documented in the schema (including the port-subtraction rule and the 120s default). The description adds no parameter-level meaning, so the baseline of 3 applies.

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 (waits) and resource (most recently started download) and adds the return value (saved file path in Chrome's download folder). It implicitly distinguishes itself from the generic browser_wait sibling, but never names that alternative, so differentiation is left to inference.

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?

"Call after clicking the download button" gives a clear triggering context and ordering. It does not state when-not to use it (e.g., vs. browser_wait) or what to do if no download was started, but the positive guidance is unambiguous.

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