drag

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

With no annotations, the description must carry full burden. It describes the sequence of events (mouse-down, move, up), return format, and a failure condition (instance is down). It references observe/settle_ms from click(), adding context.

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 (three sentences), front-loads the purpose and action, then covers return and failure. No wasted words.

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?

While the description covers core behavior and return values, it lacks detail on many optional parameters (button, observe, instance, settle_ms) and does not specify timeout or edge cases. With 8 parameters and no output schema, more completeness would be beneficial.

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 description should add meaning. It explains x1,y1,x2,y2 as start and end points, and mentions button, observe, instance, settle_ms with a reference to click(). However, it does not elaborate on default values or behavior of all parameters.

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 it performs a drag action (mouse-down → move → up) between two points, and lists use cases (drawing, selecting, sliders). This distinguishes it from siblings like click or move_mouse.

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?

The description mentions use cases but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among siblings. The mention of failure when instance is down is a helpful constraint.

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