browser_drag

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

No annotations are provided, so the description must disclose behavioral traits. It does not state whether the tool waits for the drop, simulates drag events, works with iframes or shadow DOM, or what happens on failure. This is a serious gap for a complex browser interaction.

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 with no redundancy, but it is under-specified rather than concisely rich. While it is not verbose, the extreme brevity leaves out essential information, making it acceptable but not exemplary.

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?

With no annotations and no output schema, the description is responsible for explaining the tool's complete behavior. It fails to mention return values, side effects, waiting behavior, or error cases. For a moderate-complexity tool, this is inadequate.

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 start_selector and end_selector, including _agent_id. The description's 'element A' and 'element B' merely restates the schema's start/end relationship without adding new semantic value, so the baseline of 3 is appropriate.

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 clearly states the action (drag) and the targets (element A to element B). It distinguishes itself from siblings like browser_drop through the verb 'drag', but it does not elaborate on whether this is a standard HTML5 drag-and-drop or a mouse event sequence.

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 this tool versus alternatives such as browser_click or browser_drop. There is no mention of prerequisites, supported element types, or scenarios where drag is appropriate, leaving the agent without usage context.

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