load_drum_kit

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

Annotations only show destructiveHint=false, which is minimal. The description fails to disclose behavioral traits such as whether the operation overwrites existing devices, creates new tracks, or has side effects. It only describes the basic loading steps.

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 a single sentence followed by a parameter list, with no unnecessary text. It is front-loaded and efficient, conveying the core action immediately.

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?

Despite having 3 parameters and zero schema descriptions, the description omits prerequisites, error scenarios, and output behavior. An output schema exists but the description doesn't reference it. The tool's impact on the session or track is not explained.

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?

The description provides examples for parameters (e.g., rack_uri: 'Drums/Drum Rack', kit_path: 'drums/acoustic/kit1'), adding value beyond the parameter names. However, it lacks precise format specifications or constraints, leaving ambiguity about valid inputs.

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 the tool's purpose: 'Load a drum rack and then load a specific drum kit into it.' This is a specific verb+resource combination, and it distinguishes from sibling tools like 'load_instrument_or_effect' which is more generic.

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 provides no guidance on when to use this tool versus alternatives like 'load_instrument_or_effect'. It does not mention prerequisites (e.g., track existence, browser availability) or when not to use it.

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