browser_drop

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'approved files' without explaining what 'approved' means, how the drop is performed (e.g., event dispatch), side effects, permissions, or what happens on success/failure. This is severely under-specified for a mutation-like browser automation action.

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 short sentence, front-loaded with the action, but it is under-specifying rather than concise. It omits critical details while leaving ambiguous terms like 'approved' and 'MIME-typed text data', so it does not fully earn 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?

Given 5 parameters, a nested object structure, no output schema, and no annotations, this description is far from complete. It does not explain return values, error conditions, how data and paths interrelate, or what 'approved' means, leaving an agent with insufficient information to invoke the tool reliably.

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 phrase 'files or MIME-typed text data' vaguely maps to the 'paths' and 'data' parameters, but the description does not clarify which parameter corresponds to which, nor the required format. With 60% schema coverage, the description adds only marginal meaning beyond the property names and lacks detail for the two undocumented 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 ('approved files or MIME-typed text data') and destination ('onto a target'). It clearly indicates this is a drop action, distinguishing it from click/type/upload siblings, though it does not explicitly contrast with browser_file_upload or 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?

No guidance is provided on when to use this tool versus alternatives like browser_file_upload or browser_drag. There are no exclusions, prerequisites, or contextual cues to help an agent decide between similar file- or drag-related operations.

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