browser_drop

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

Annotations are absent, so the description alone must disclose side effects and execution traits. It states only the mechanical action and gives no indication that the drop is synthesized, whether it can trigger navigation or file-handling side effects, or whether permissions are required. This is a meaningful transparency gap.

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 that packs the action, payload alternatives, and targeting mechanism without filler. It is appropriately concise for a well-schematized tool.

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 rich 100% parameter schema, the description covers the essential invocation path: it names payload modes and the target. It still leaves behavioral details such as synthetic-event semantics and post-drop effects to inference, but this is not fatal for a simple drop action.

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 description coverage is 100%, so the baseline is 3. The prose echoes `paths`, `data`, and `ref`/selector targeting but adds no meaning beyond the schema; the schema itself documents the payload formats. No deduction needed.

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 names a specific action (`Drop`), the two accepted payload kinds (`paths` for files, `data` for MIME data), and how to target an element (`ref` or selector). This is sufficiently distinct from sibling actions like `browser_click`, `browser_type`, and `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?

It clearly conveys the intended use case — dropping local files or in-memory MIME data onto a page element — and how to address the target. It does not explicitly name alternative tools or exclusion cases, but the context is specific enough to guide selection.

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