wait_for_download

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

With no annotations, the description carries the full burden. It mentions clicking and waiting but omits critical details: what happens if no download occurs, timeout behavior, error handling, or whether the tool returns the download status. The description is insufficiently transparent.

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 short (3 words), which is concise but borderline too terse. It front-loads the action but lacks structure or additional context. Could be improved with a brief phrase about the trigger_selector role without adding length.

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 presence of an output schema and 1 parameter (with 0% schema description coverage), the description is incomplete. It does not describe the return value, wait duration, or error scenarios. Among many sibling tools, its unique role is underspecified.

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 add value. The description uses the phrase 'click trigger' which relates to the parameter 'trigger_selector', but does not explain that it is a CSS selector for the element to click. No additional semantics beyond the parameter name 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?

The description clearly states the action: click a trigger and wait for a file download. It distinguishes from siblings like 'click' (which just clicks) and 'wait_for' (generic wait) by specifying the download context. However, it is somewhat terse and does not define 'trigger' explicitly.

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 is provided on when to use this tool versus alternatives such as 'click' plus 'wait_for', or 'wait_for_response'. There is no mention of prerequisites or exclusions, leaving the agent to infer usage context.

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