ableton_reorder_device

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

No annotations provided; description only says 'move', omitting any side effects, constraints (e.g., on indices), or impact on device settings. Does not disclose behavior fully.

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?

One sentence is concise and front-loaded, but too brief for the tool's complexity. Could add 1-2 sentences on parameters and behavior.

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 3 required params (including nested object), no annotations, no output schema, the description fails to convey constraints, return values, or usage context.

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?

Description provides no parameter meaning; despite 0% schema coverage, it does not explain location, deviceIndex, toIndex. Agent relies solely on schema structure.

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?

Clearly states 'Move a device within a track, return, or master device chain', specifying verb, resource, and domain. Distinguishes from sibling tools like load_device or delete_device.

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 reorder vs other device operations. No mention of prerequisites or context for use.

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