load_drum_pad

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is largely covered. The description adds the useful mapping '36 = C1 = first pad', but says nothing about whether loading replaces existing pad content, what happens if the track is not a Drum Rack, or how query/uri interact when both are supplied.

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?

Two compact sentences with the core action front-loaded and no filler. The parameter notes are appended efficiently, though the parenthetical pad-numbering aside slightly interrupts the flow of the main instruction.

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?

An output schema exists, so return values need not be described, and the annotations cover mutability. Still, for a mutation tool with 0% schema description coverage, the definition omits the track_index meaning, the mutual exclusivity of query and uri, and the effect on any sample already occupying the pad.

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 description coverage is 0%, so the description carries the burden and it partially delivers: it explains query as a browser search string, uri as an exact search_browser result, and note as the pad identifier with 36 = C1. It leaves track_index completely undefined and does not state that query and uri are alternatives rather than combinable 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 gives a specific verb and resource ('Load a sample or instrument ... onto one Drum Rack pad'), which clearly separates it from siblings like load_drum_kit (a whole kit) or load_sample (generic sample loading). It stops short of explicitly naming those siblings, so 4 rather than 5.

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?

It explains how to choose between the two source parameters (query for fuzzy search, uri for an exact search_browser hit), which is useful routing guidance. However, it gives no guidance on when to use this tool versus load_drum_kit, load_sample, or load_browser_uri, and it never states prerequisites such as the target track already being a Drum Rack.

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