playwright__browser_drop

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds helpful context about external-drag semantics and MIME-typed data, but it does not disclose likely page-side effects such as uploads, navigation, or handlers triggered by the drop.

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 concise, front-loaded with the action, and every sentence contributes useful information. The essential constraint is stated clearly without unnecessary detail.

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 4-parameter tool with no output schema, the description and schema together give enough to call the tool correctly: target selection, paths/data alternatives, and drop behavior. It is slightly incomplete on when to prefer this over file_upload or drag, and on expected return/result behavior, but those are minor gaps.

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 schema already documents each parameter. The description adds value by stating the 'at least one of paths or data' constraint and clarifying that data is a MIME-type-to-value map, which is not fully explicit in the schema.

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 verb ('Drop') and resource ('files or MIME-typed data onto an element'). 'As if dragged from outside the page' clearly distinguishes it from in-page drag tools like playwright__browser_drag.

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 gives the key precondition that at least one of 'paths' or 'data' must be provided. However, it does not explicitly explain when to choose this over alternatives such as playwright__browser_drag or playwright__browser_file_upload, so usage guidance is only implied.

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