browser_drop

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not responsible for repeating that. It adds useful context about simulating an external drag, but does not disclose any additional behavioral details such as triggered page handlers or side effects. There is no contradiction with the 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 two short sentences with no filler. The core action is front-loaded, and the essential constraint about paths/data is placed directly after. Every word contributes to understanding.

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 100% schema coverage and the annotations covering destructive behavior, the description is sufficiently complete for correct invocation. It covers the critical constraint and the simulation semantics, though it does not elaborate on edge cases like providing both paths and data.

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%, so the baseline is 3. The description adds meaningful parameter semantics beyond the schema by stating 'At least one of paths or data must be provided', which is a cross-parameter constraint not expressed in the JSON schema itself.

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 action ('Drop files or MIME-typed data onto an element') and adds the key distinction 'as if dragged from outside the page', which separates it from siblings like browser_drag. It clearly identifies the resource and the mechanism.

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 implies when to use the tool: when an external drag-and-drop simulation is needed. However, it does not explicitly compare against alternatives such as browser_file_upload or browser_drag, nor does it state when not to use this tool.

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