load_drum_kit

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

With no annotations, the description must cover behavioral traits, but it only describes the basic operation: loading a drum rack then a kit. It does not disclose side effects (e.g., overwriting existing clips), required track state, error conditions, or the output schema. This is insufficient for full behavioral transparency.

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 short, front-loaded with the main purpose, and then presents a clear, enumerated parameter list. Every sentence serves a purpose with no redundancy.

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 3 required parameters and no annotations, the description covers the parameters but lacks details about preconditions (e.g., the track must exist and be a MIDI track), postconditions, and the output schema. Additional context on return values or error handling would improve completeness.

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 input schema has 0% description coverage, but the tool's description provides explicit explanations for all three parameters: track_index, rack_uri, and kit_path, including an example for kit_path. This adds significant value beyond the bare schema.

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 action: 'Load a drum rack and then load a specific drum kit into it.' It specifies the two-step process and lists the exact parameters, making the purpose unambiguous. It distinguishes from sibling tools like load_instrument_or_effect by focusing on drum-specific loading.

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 is provided on when to use this tool versus alternatives such as load_instrument_or_effect. The description does not mention prerequisites, typical use cases, or when not to use it, leaving the agent to infer from the name alone.

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