browser_file_upload

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

Annotations already declare destructiveHint=true (file upload can overwrite or cause side effects), readOnlyHint=false, and openWorldHint=true (may affect external state). The description 'upload' adds minimal behavioral context beyond annotations—no mention of file type/size limits or what happens on cancellation. However, no contradiction with annotations.

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, concise sentence. It is front-loaded with the action and resource. No wasted words, though it could be slightly more specific (e.g., mention file input context).

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?

For a tool that uploads files with no output schema and only one parameter, the description lacks context on expected file types, size limits, and typical usage (e.g., must be called after focusing a file input element). It is barebones and assumes agent knowledge.

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' property explains absolute paths and the omission cancels). The description adds no new parameter meaning beyond 'paths'—it just restates 'files'. The cancellation behavior is in the schema, not the description, so no additional value.

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'), and the input schema confirms it handles files via paths. It distinguishes from sibling browser tools (e.g., browser_drop, browser_click) which have different purposes.

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 explicit guidance on when to use this tool vs alternatives like browser_drop for file interactions. No mention of prerequisites (e.g., a file input element must be focused) or when to cancel (omit paths). The context is implied but lacks actionable direction.

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