browser_drag

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

The annotations already mark this as non-read-only and destructive, so the description does not need to repeat that. However, the description itself adds no additional behavioral detail about side effects, drop events, or state changes.

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 concise sentence with no filler or redundant detail, conveying the action and its object efficiently.

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 simple two-element drag action, the description plus schema is sufficient to understand what the tool does and what inputs are required. It omits output/return detail, but no output schema is specified and action tools of this kind commonly return no meaningful value.

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 input schema fully describes all four parameters, including target references and human-readable descriptions. The tool description adds no extra parameter semantics beyond what the schema already provides, so the baseline score applies.

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 'Perform drag and drop between two elements' uses a specific verb and resource, and clearly distinguishes this tool from sibling actions like click, hover, and drop by identifying the drag-and-drop interaction.

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 clearly indicates the tool is for drag-and-drop interactions between two elements, making the primary use case obvious. It does not explicitly contrast with alternatives such as browser_drop, but the context is clear enough for selection.

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