Upload files

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

The description adds no behavioral traits beyond what annotations already provide (destructiveHint=true, readOnlyHint=false, openWorldHint=true). It does not explain what 'upload' means in a browser context (e.g., whether it triggers a network request, requires a specific page element, or has side effects). With no output schema and minimal description, the agent is left guessing.

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 (4 words), but this brevity comes at the cost of essential information. It is under-specified rather than concise. A better description would include parameter hints or usage context without being verbose.

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 complexity (destructive, open-world, 2 parameters no schema descriptions, no output schema), the description is woefully incomplete. It fails to explain how to use the 'paths' parameter, what the tool does in the browser, or what the result will be. An agent cannot reliably invoke this tool based on this description alone.

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 description does not explain the two parameters ('_meta' and 'paths') at all. With 0% schema description coverage, the description must compensate, but it only repeats the overall purpose. An agent cannot infer what 'paths' expects (local file paths, URLs, or something else) or what '_meta' is for.

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' uses a specific verb ('upload') and resource ('files'), and clearly distinguishes this tool from siblings like 'browser_navigate' or 'browser_click' which have no upload capability. The addition of 'one or multiple' adds specificity beyond the title.

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 provides no guidance on when to use this tool, what prerequisites are needed (e.g., a file input element on the page), or any alternatives. Without such context, an agent may misuse it in situations where upload is not applicable.

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