Drag mouse

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

Annotations already declare destructiveHint=true, implying mutation. The description confirms a drag-and-drop action, which is inherently mutable, but does not add context beyond annotations—e.g., it does not mention that elements might be moved, that the operation may trigger events, or that it could fail if elements are not draggable. No contradiction with annotations.

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 sentence of 7 words, which is concise, but it lacks structure (no bullet points, no front-loaded key info). It is not verbose, but it also does not earn its place by adding significant value beyond the tool name.

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 complexity (5 parameters, no output schema, no schema descriptions, and annotations indicating a destructive/stateful action), the description is insufficient. It does not address return values, error conditions, or how to specify elements. The agent cannot reliably invoke this tool correctly with the given information.

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 0%, meaning the description carries full burden for parameter meaning, but it provides none. The description does not explain what 'startTarget', 'endTarget', 'startElement', or 'endElement' are (e.g., CSS selectors, XPath, element IDs). For a tool with 5 parameters and no schema descriptions, this is a major gap.

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 states 'Perform drag and drop between two elements', which clearly identifies the action as a drag-and-drop operation between elements. However, it does not distinguish this from the sibling 'browser_drop' tool; the name 'browser_drop' already implies a drop action, and the description here adds no differentiation.

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 provided on when to use this tool versus alternatives like 'browser_drop', or on prerequisites such as the page needing to be interactive or elements needing to be selectable. The description lacks any context about required conditions or exclusions.

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