Click And Download

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

Annotations already convey readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=false. The description adds context about awaiting download completion and returning a receipt, but it does not clarify what makes the action destructive or what side effects occur (e.g., file saving location, overwrite behavior). This is acceptable but not rich.

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 a single sentence that efficiently conveys the core action and result. It is front-loaded with the verb 'Perform' and wastes no words, earning a top score.

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?

The schema is rich and includes an output schema, so return values are covered. However, the description omits the 'accessibility' trigger type (AccessibilityTargetInput) from its list of 'selector, coordinate, or keyboard trigger,' and does not mention optional constraints like expected_filename or operation_key. This is a noticeable gap for a tool with multiple input variants.

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 parameters like timeout, selector, operation_key, expected_filename, and expected_mime_type are already well-documented. The tool description adds no parameter-specific meaning, so the baseline score of 3 is appropriate.

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: perform a trigger (selector, coordinate, or keyboard), await a download, and return an integrity-checked receipt. This distinguishes it from siblings like element_click (just clicks) and element_click_and_upload (handles uploads), making the purpose unambiguous.

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 description implies this tool is for triggering and completing a download, but it does not explicitly state when to use it versus alternatives, nor does it provide exclusions or prerequisites. The unique behavior is implied by 'await one completed download' but no direct guidance is given.

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