garageband_window_drag

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

No annotations provided, so description must disclose behavior. It only states the action ('drag') without explaining the mechanism (e.g., whether it holds mouse button, if there is a release event, or any side effects). Missing details like drag speed or modfiers.

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, no unnecessary words. Efficiently conveys the core function.

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 no annotations or output schema, description is too sparse for a 5-parameter function. Missing details on coordinate system specifics, what constitutes a drag, and expected return. User would need to infer much from the name alone.

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 has 0% description coverage. Description says 'window-relative macOS point coordinates' but does not clarify that (x1,y1) is start and (x2,y2) is end, nor explain delay_seconds. Parameter meaning is heavily implied, not explicit.

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 specifies the action ('drag'), the resource ('GarageBand window'), and the coordinate system ('window-relative macOS point coordinates'). This differentiates it from sibling tools like garageband_window_click (click) and garageband_window_rect (rect).

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. For example, does not mention that dragging requires a previous click or that it is for moving UI elements. Lacks context for proper selection.

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