browser_wait_for_download

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

No annotations provided. Description discloses default timeout and that it returns path, but does not explain blocking behavior, failure handling, or return format. Adds some value but omits important behavioral details.

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?

Two short sentences conveying essential information with no redundancy. Purpose and default timeout are front-loaded.

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?

Adequately covers the tool's simple functionality: waits, uses timeout, returns path. Could mention that it assumes a download is already in progress, but not strictly necessary.

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 100% for the single parameter 'timeout' with description 'Timeout in ms'. Tool description adds the default value '30s', which provides meaningful extra context beyond the schema.

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 action (wait for download to complete) and result (get path), with specific resource (download). Distinguishes from sibling browser_wait by specifying download context.

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?

Implicitly states when to use (when expecting a download), but lacks explicit exclusions or alternatives. However, the specific download context differentiates it from general wait tools.

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