playwright__browser_file_upload

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

Annotations already indicate destructive, non-read-only, and open-world behavior. The description adds no behavioral context beyond 'upload', such as side effects, interaction with the file chooser dialog, or state changes. The description adds minimal value over annotations for understanding implications.

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 concise (two words plus a brief schema). It front-loads the verb and resource. However, it could be expanded slightly to include context without being verbose, but for a simple tool this is adequate.

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 simple parameter set, high schema coverage, and presence of annotations, the description is minimally adequate. It covers the basic action but lacks information about when the file chooser appears, whether the element must be an input[type=file], or how it interacts with other browser tools.

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% for the single parameter 'paths', which explains absolute paths, single/multiple files, and cancellation. The tool description adds no additional parameter meaning, so baseline 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 'Upload one or multiple files' clearly states the verb (upload) and resource (files). It distinguishes from sibling browser tools like navigate, click, and filesystem tools because 'upload' is specific to file selection in a browser context. However, it does not specify the target (e.g., to a file input element), which slightly reduces clarity.

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. Siblings include filesystem write tools, but no context is provided about prerequisites (e.g., a file input must be focused) or when to avoid using it. The schema mentions cancellation, but overall usage direction is missing.

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