add_device

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

No annotations provided, and description only says 'add' without disclosing side effects (e.g., whether device is appended or inserted, failure modes, or track index bounds). Lacks operational details expected for a mutation tool.

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?

Three sentences, front-loaded with core purpose, efficient examples, and prerequisite. 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?

Covers device types and prerequisite, but misses details like track index interpretation, return value (though output schema exists), and behavior (e.g., position in chain). Adequate but not thorough for a 2-parameter tool with no annotations.

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%; description provides examples for 'device_name' but does not explain 'track_index' semantics (e.g., zero-indexed, valid range). Insufficient guidance for correct parameter specification beyond naming.

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 action ('Add a device or plugin to a track') and scope ('by searching Ableton's browser'). Distinguishes from siblings like 'add_device_to_return' and 'delete_device' by specifying regular tracks and device types.

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?

Provides clear usage context: works for Ableton native and VST plugins, with examples. Includes prerequisite ('Plugin must be installed and scanned'). Does not explicitly exclude cases or contrast with alternatives, but context is sufficient for typical use.

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