load_drum_kit

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

Discloses the two-step mutation process, potential failure mode (empty rack remains), and that repeated calls add more racks. Annotations are minimal (non-idempotent, non-destructive) and description adds crucial context.

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?

Description is somewhat long but each sentence serves a purpose. Well-structured: action, prerequisites, behavior, alternative.

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?

Given 3 required params, 100% schema coverage, and output schema present, the description covers purpose, prerequisites, side effects, and alternatives completely.

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 100%, but description adds value by explaining the relationship between rack_uri and kit_path, giving an example for kit_path, and clarifying track_index is zero-based.

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 the action: load a Drum Rack and then the first loadable kit at a browser path. Distinguishes from sibling tool load_instrument_or_effect by specifying the two-step process.

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?

Explicitly tells when to use prerequisites: search_browser and get_browser_items_at_path. Provides clear alternative: use load_instrument_or_effect for a single known URI.

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