browser_drag

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description only says 'Drag from one ref to another,' revealing nothing about side effects, event triggers, or state changes. This is a significant gap for a browser interaction tool.

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, which is concise, but it under-specifies the tool's operation. It lacks necessary details about parameters and behavior, so the brevity is not valuable; it is merely incomplete.

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 four required parameters, no annotations, and no output schema, the description is severely inadequate. It does not explain what a ref is, what an element is, or the effects of the drag. The tool is essentially opaque to the agent.

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 schema has zero description coverage, and the description does not compensate. It mentions 'ref' but does not explain the distinction between startRef, endRef, startElement, and endElement. The parameter semantics remain completely undocumented.

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 the verb 'drag' and the resource 'from one ref to another,' indicating a drag operation. However, it does not explain what a 'ref' is or what the drag achieves, making the purpose vague. It does not distinguish from sibling tools like click or hover beyond the action name.

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. It does not mention scenarios for using drag over click or hover, nor any prerequisites or context. The description provides no usage direction.

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