browser_drop_file

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

With no annotations, the description carries the full behavioral burden. It discloses the search scope (subtree or parent up to 2 levels), what happens when no input is found (clear error), and the limitation for pure drop-zones. It could further clarify whether file and files are mutually exclusive or what happens on success, but the core behavior is well covered.

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?

Three sentences with no fluff: the action is front-loaded, the usage condition follows, and the failure/limitation is stated last. Every sentence earns its place.

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 description covers the trigger scenario, search behavior, error case, and manual-handling limitation, which is sufficient for an agent to decide and invoke it. The only minor gap is the absence of success-return details, but there is no output schema to satisfy and the practical usage is clear.

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 coverage is 100%, so the baseline is 3. The description connects the selector to the drop-zone target and explains how the hidden input is located, which adds some context, but it does not substantially refine the meaning of file or files beyond their schema descriptions.

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 states a specific mechanism — uploading via a hidden file input within a drag-drop zone — and names the exact condition that distinguishes it from browser_upload_file. This makes the tool's purpose immediately recognizable and differentiated from sibling 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?

It explicitly says when to use the tool: when browser_upload_file fails because the dropzone has no visible file input. It also gives a clear when-not-to-use hint by noting pure drop-zones without backing inputs require manual handling.

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