browser_handle_download

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds context about intercepting the download event and saving to workspace, which is useful. However, it does not disclose specifics like overwrite behavior, file naming conflicts, permissions, or what happens if the download fails, so it only partially adds value beyond annotations.

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, front-loaded with the main action ('Clicks'), and contains no filler. Every word adds meaning, making it highly concise and well-structured.

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?

With only two parameters and no output schema, the description covers the core action but omits important details such as the return value (e.g., saved file path), potential destructive side effects (e.g., overwriting files), and where exactly in the workspace the file is saved. Given the tool's simplicity, it is minimally complete but has gaps.

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%, with clear descriptions for both 'target' (selector or snapshot ID) and 'filename' (optional custom name). The tool description does not add additional parameter meaning beyond what the schema already provides, aligning with the baseline of 3.

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 uses a specific verb ('Clicks') and identifies the resource (element triggering download) and the outcome (intercepts download event, saves file to workspace). It clearly distinguishes from sibling tools like browser_click (just clicks) and browser_file_upload (uploads), making its 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 the tool is intended for clicking elements that trigger downloads and saving the resulting file, but it does not explicitly state when to use it over alternatives (e.g., browser_click) or mention exclusions. The context is clear enough for an experienced agent, but no explicit guidance is provided.

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