Upload files to browser

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

Annotations already state destructiveHint=true and readOnlyHint=false. The description adds that this tool transfers files and sets the input, which is a useful behavioral outcome. It does not disclose potential side effects like overwriting existing state or triggering change events, but the annotations cover the main safety traits.

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, tightly-worded sentence with zero filler. The action is front-loaded and every word adds meaning.

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 nested target object is complex, yet the description offers no guidance on how to specify the target (e.g., by coordinates, locator, or elementId), nor does it mention timeoutMs or return behavior. There is no output schema and the description leaves too much to inference for a tool with this many target options.

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?

With 0% schema description coverage, the description partially compensates by indicating that 'paths' corresponds to files or directory contents and 'target' identifies the file input. However, it does not explain how to choose among the numerous target sub-fields (coordinates, locator, elementId) or what timeoutMs does.

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 ('Transfer') and resource ('files or directory contents') and clearly states the subsequent action ('set the targeted file input'). This distinguishes it from the sibling browser_download_file and other browser tools.

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 usage context: it is the tool to use when files need to be placed into a browser device and a file input must be set. The mention of 'selected browser device' and 'targeted file input' gives clear context, though no explicit alternative tools are named.

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