browser_download_file

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It fails to mention side effects such as triggering a browser download, whether it waits for the download to complete, any permission requirements, or how it interacts with the page. The description is a bare label with no operational detail.

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 extremely short, which could be seen as concise, but it is under-specified to the point of being a restatement. There is no front-loaded useful detail, and it does not earn its place by adding value beyond the tool name.

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 tool's apparent function (triggering a file download via a DOM selector), the description provides no information about return values, download behavior, waiting logic, or error conditions. With no output schema and no annotations, the description is wholly inadequate for an agent to invoke this tool correctly.

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?

The schema has a single parameter 'triggerSelector' with no description, and schema description coverage is 0%. The description does not explain what the selector refers to or how it is used to initiate a download, leaving the agent to guess the parameter's semantics entirely.

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 '下载文件' (Download file) is essentially a restatement of the tool name, providing no additional detail about what file is downloaded or how. It does not differentiate from sibling tools like browser_upload_file beyond the obvious inverse action, and the 'triggerSelector' parameter suggests it triggers a download via a UI element, which is not mentioned.

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?

There is no guidance on when to use this tool versus alternatives. It does not explain that it requires a selector to trigger a download, nor does it mention any prerequisites or scenarios where it should be preferred over other browser actions.

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