browser_drag

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

With no annotations provided, the description carries the full burden of disclosing behavior. It does not mention that a drag-and-drop involves source and target selectors, what events are triggered, or any side effects. The one-word description offers no insights beyond what the tool name already implies.

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 an under-specified fragment rather than a concise explanation. It provides zero information beyond the tool name and is not adequately structured to inform the agent in any meaningful way.

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 complete lack of annotations, output schema, and any parameter explanation, this description is entirely inadequate. An agent would have no way to understand how to invoke browser_drag correctly, what the two selectors are for, or what outcome to expect.

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 defines sourceSelector and targetSelector as required strings, but the description does not explain their purpose or how they relate to the drag operation. Since schema description coverage is 0%, the description should compensate, but it fails to add any meaning to the 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 '拖拽元素' simply translates to 'drag element', which is a tautology of the tool name 'browser_drag'. It does not specify that this is a drag-and-drop operation between source and target selectors, nor does it distinguish it from other browser interaction tools like browser_mouse_move or browser_click.

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 given on when to use browser_drag versus other browser_* tools. The description provides no context about the operation's purpose or when it should be preferred, leaving the agent without any decision support.

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