browser_drop

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

Annotations already mark destructiveHint as true, and the description aligns by stating 'Drop...' implying mutation. The description adds valuable context by specifying it simulates an external drag-and-drop, which goes beyond what annotations provide. No contradictions.

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 sentences, no extraneous information. Every part contributes: the action, the simulation aspect, and the parameter constraint. Highly efficient.

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's moderate complexity (4 parameters, nested data object, no output schema), the description covers the core functionality and a key constraint. It could further elaborate on typical use cases or interactions with other browser tools, but is largely sufficient.

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 usage condition ('At least one of paths or data must be provided') not enforced by the schema. It also implicitly clarifies the purpose of each parameter. While not exhaustive, it adds meaningful semantic value.

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?

Description clearly states the action ('Drop files or MIME-typed data') and target ('onto an element'), with a specific simulation context ('as if dragged from outside the page'). It effectively distinguishes from sibling tools like browser_drag, which likely handles internal drag-and-drop.

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 description provides a necessary constraint ('At least one of paths or data must be provided') but lacks explicit guidance on when to use this tool over alternatives such as browser_file_upload for standard file inputs. No comparison with siblings is given.

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