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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the drag uses real mouse events, whether it waits for completion, what permissions or tab state are required, or what side effects occur; only the coordinate frame is implied.

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 single sentence is front-loaded and waste-free, but it is under-specified rather than appropriately concise. It does not provide structural cues about required parameters or sequencing.

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 six-parameter browser-action tool with no annotations and no output schema, the description is too thin. It omits tab scoping, the purpose of notification_message, coordinate semantics, and any indication of return or error behavior.

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 only 17%, and the description adds just the 'viewport coordinates' meaning for the four coordinate parameters. It leaves tab_id and notification_message unexplained and does not clarify coordinate units or origin, so it only partially compensates for the sparse schema.

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 a specific verb ('drag') and locational frame ('viewport coordinates'), so the basic action is inferable. However, it does not specify what is being dragged (mouse pointer, element, selection) or how this differs from siblings like browser_mouse_click_xy or browser_interact.

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?

There is no guidance on when to use this tool versus alternatives such as browser_mouse_click_xy, browser_interact, or browser_dom_input. No prerequisites, exclusions, or contextual triggers are mentioned.

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