browser_drag

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

No annotations are provided, so the description must fully disclose behavior. It states 'Returns a snapshot' but does not mention if the drag is a user simulation, whether it triggers events, or any side effects like scrolling or state changes. The behavioral transparency is insufficient.

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 very concise with two short sentences. It gets straight to the point without unnecessary words. However, it is perhaps too brief, but conciseness is still good.

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 tool's complexity (drag and drop) and no annotations, the description is incomplete. It does not explain how to obtain refs, the prerequisites (e.g., active session), or the nature of the snapshot. The output schema exists but is not detailed; the description should still provide context.

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 coverage is 0%, so the description must add meaning. It uses 'by refs' to hint at element references, but does not explain what refs are or the format expected. The session_id parameter is not mentioned at all. Minimal value added beyond the 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 clearly states the action ('drag') and the resources ('one element onto another by refs'). It indicates that it returns a snapshot, and it distinguishes from other mouse-based drag tools like browser_mouse_drag by specifying 'by refs'. However, it does not explicitly differentiate from all sibling tools.

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 (e.g., browser_mouse_drag). The description does not mention prerequisites or context for use, leaving the agent to infer usage.

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