load_drum_pad

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

The annotations already establish that this is a destructive, non-idempotent write operation. The description adds substantial detail beyond that: external files are staged under Samples/Imported/Maestro without overwriting files, existing incompatible pads are refused, source bytes/attack marker/Warp state are verified, and percussion uses one-shot mode.

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 leads with the core purpose and then compresses prerequisites, staging behavior, refusal rules, and verification into three dense sentences. It is front-loaded and free of filler.

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 the rich schema, output schema, and annotations, the description supplies the important operational context an agent needs. It does not fully address whether an existing simple pad is replaced or how the confirm parameter interacts with destructive behavior, but it is largely complete.

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 100%, so the schema itself documents all five parameters thoroughly. The description adds some contextual meaning around audio staging and attack verification, but it does not explain key parameters such as confirm, pad_note, or rack_path.

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 file onto a Drum Rack pad. It also clarifies the special case of creating an empty pad's Simpler, which distinguishes it from generic sample-loading siblings.

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 states a prerequisite for empty pads and a refusal condition for existing layered/non-Simpler pads, giving clear when-to-use and when-not-to-use guidance. It does not explicitly name alternative tools such as load_sample or write_drum_clip for other routing needs.

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