browser_drop

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

Annotations indicate destructiveHint and openWorldHint, so description adds 'as if dragged from outside the page' which clarifies the simulation. However, it does not detail potential side effects like triggering event handlers or page navigation.

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?

Two concise sentences with the core purpose front-loaded. Every word is meaningful and no redundancy.

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 is adequate for a simple drop action, but given destructive and open-world annotations, it lacks details on what happens after drop (e.g., event triggering, return value). The schema covers parameters well, but behavioral outcomes are not specified.

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%, but the description adds a critical constraint not in schema: 'At least one of paths or data must be provided.' This clarifies optionality beyond the required fields.

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 clearly states the tool drops files or MIME-typed data onto an element simulating an external drag. It distinguishes from siblings like browser_drag by specifying 'dragged from outside the page' and from browser_file_upload by referring to drop behavior.

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 over alternatives like browser_drag or browser_file_upload. The hint 'At least one of paths or data must be provided' is a constraint, not a usage guideline.

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