browser_file_upload

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, but the description adds no behavioral context beyond the act of uploading. The schema notes that omitting paths cancels the file chooser, but the description itself does not explain side effects, what gets overwritten, or how the upload interacts with the current page.

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 front-loaded sentence with no filler words. It is appropriately brief for such a simple tool, though the brevity sacrifices useful usage and behavior guidance.

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 schema and annotations cover the core parameter and safety profile, making this minimally viable for a one-parameter tool. However, the description lacks guidance on when to use upload vs browser_drop, how the target file input is determined, and what observable effects occur, so it is not fully complete.

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%: the paths parameter is documented as absolute paths, single or multiple, and omitting it cancels the file chooser. The description does not add any semantics beyond what the schema already provides, so the baseline of 3 applies.

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 says 'Upload one or multiple files,' giving a clear action and object with multi-file scope. It is not a tautology and is distinguishable from siblings like browser_drop, though it does not specify that this operates through the browser file chooser or how the target element is selected.

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?

No guidance is given about when to use this tool versus sibling tools such as browser_drop or browser_fill_form. The description does not mention prerequisites, target element requirements, or alternatives, so the agent must infer usage from the tool name and schema.

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