browser_drop

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the risk profile is covered. The description adds the external-drag simulation framing and the required-input constraint, but says nothing about what side effects a drop triggers (upload handlers, navigation, listeners) or the permission role of the 'element' parameter.

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 short sentences, no filler, with the core action first and the precondition second. Every clause 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?

For a destructive, open-world interaction tool with a nested 'data' object and no output schema, the description is thin: it omits what a successful drop produces, what the 'element' parameter does for permissions, and whether dropped files must exist locally. Adequate to call, but not complete.

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 baseline is 3, but the description adds a real constraint not encoded in the schema: the schema requires only 'target', while the description imposes that at least one of 'paths' or 'data' must be supplied. That is meaningful beyond what the structured fields say.

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?

States a specific verb (drop) and resources (files or MIME-typed data) plus the semantic framing 'as if dragged from outside the page,' which implicitly separates it from browser_drag (in-page drag) and browser_file_upload (file input). It never names those siblings explicitly, so the differentiation is inferable rather than stated.

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 only guidance given is a precondition ('at least one of "paths" or "data" must be provided'), which is a constraint rather than a when-to-use rule. Nothing tells the agent when to prefer this over browser_file_upload or browser_drag, and no exclusions or prerequisites are stated.

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