zen_drag

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

With no annotations, the description is the only source but fails to disclose key behavioral traits such as whether elements need to be draggable, the simulation of drag events sequence, or scroll handling. Only 'synthetic' and 'HTML5 drag events' are mentioned.

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 concise sentence but lacks structure or additional details. It is front-loaded but arguably too brief to be effective.

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 three parameters and no output schema or annotations, the description is severely incomplete. It omits critical context like selector interpretation, tab context, and return value, leaving the agent underinformed.

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 description does not add any meaning to the parameters (from_selector, to_selector, tab_id) beyond what the schema provides. With 0% coverage, it fails to explain that selectors are CSS selectors or that tab_id is optional.

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 tool performs a synthetic drag-and-drop operation from one element to another, using HTML5 drag events. It uniquely identifies the tool among siblings like zen_click and zen_hover.

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 like zen_hover or zen_click. There is no mention of prerequisites or preferred contexts.

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