nex_browser_drop

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

No annotations are present, so the description must disclose behavioral traits on its own. It fails to explain what 'approved files' means, whether drop triggers native drag-and-drop events or just sets data, how MIME-typed data is formatted, or any side effects on the page. The agent cannot predict what happens after invoking this tool.

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 a single, front-loaded sentence with no wasted words. It could have been structured to include examples or a brief usage scenario without becoming verbose. Still, it is concise and easy to read, though it sacrifices helpful detail for brevity.

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 tool has 5 parameters, a nested object, and no output schema, this description is far too thin. It does not explain how the data/paths parameters interplay, what happens on success or failure, whether an element must be visible/enabled, or how to reference the target reliably. An agent operating on a live browser would need more context to use this tool correctly and safely.

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?

The schema covers 60% of parameters with descriptions, so the description's compensation requirement is moderate. The description adds some meaning: 'files' maps to 'paths' and 'MIME-typed text data' maps to the 'data' object, and 'target' is clearly the drop receiver. However, it does not explain how 'data' should be structured (property names, values) or how 'paths' are treated, leaving ambiguity for the two underlying payload parameters.

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 uses a specific verb 'drop' and identifies the resource ('target'), and mentions two distinct payload types (files, MIME-typed text data). It is clear enough to distinguish from siblings like nex_browser_file_upload (which likely uploads via a file picker) and nex_browser_drag (which drags UI elements). However, 'approved' is vague and could confuse an agent about whether some pre-authorization is required.

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 guidance is provided about when to use this tool compared to alternatives such as nex_browser_file_upload, nex_browser_drag, or nex_browser_fill_form. The description does not state whether it simulates native drag-and-drop events, whether it works on all selectable targets, or any prerequisites. The agent is left to infer usage from the verb and parameter names.

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