garageband_loop_drag

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

Mentions 'guarded-drag' and that dragging may trigger Apple's content installer, adding context beyond a simple drag. Without annotations, this provides some behavioral insight but lacks details on success/failure or other side effects.

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?

Two concise sentences that efficiently convey the tool's core action and a critical requirement. No unnecessary 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?

For a tool with 9 parameters, no output schema, and no annotations, the description is grossly insufficient. It does not explain most parameter semantics, return behavior, or potential side effects beyond the installer dialog.

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 description coverage is 0%. Only the 'acknowledge_content_install_risk' parameter is explained in the description. The other 8 parameters (query, index, coordinates, etc.) receive no semantic context, leaving the agent with the schema alone which has no descriptions.

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?

Description clearly states the tool searches and drags a loop row, distinguishing it from sibling tools like garageband_loop_search and garageband_loop_select. It specifies 'guarded-drag' and the required acknowledgment.

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?

Describes the need to acknowledge content install risk for downloadable rows, implying a prerequisite condition. However, it does not explicitly state when to use this tool over alternatives (e.g., loop_search, loop_select).

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