drag

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

Annotations provide no safety hints (readOnlyHint=false, destructiveHint=false, so no special behavior). Description does not disclose potential side effects, whether it simulates click-drag-release, or if coordinates are relative to screen or app window. Behavioral traits are underspecified.

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?

Single sentence, front-loaded with action and coordinate system. No extraneous words. Concise and to the point.

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?

Adequate for a simple drag tool with no output schema and all parameters described. However, it lacks details about the expected behavior (e.g., whether it performs a click-drag-release sequence, or if it works on scrollable areas). Could be more complete.

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 100% with each parameter having a brief description. The tool description adds no extra semantic meaning beyond the schema itself. Baseline score of 3 is appropriate as schema does the work.

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 from one point to another') and the coordinate system ('pixel coordinates'). It distinguishes from sibling tools like click and scroll, which involve different gestures. However, it could be more specific about what kind of drag (e.g., mouse drag on UI element).

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 on when to use this tool versus alternatives like scroll or set_value. No mention of prerequisites or context (e.g., app must be frontmost). The description is purely functional without usage context.

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