load_instrument_or_effect

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

There are no annotations, so the description is the only source of behavioral information. It only states the action (load) without disclosing side effects, required permissions, reversibility, or error conditions. It does not mention what happens to existing devices on the track or whether the action can be undone. This is a significant gap for a mutation tool.

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 concise, starting with the core purpose and then listing parameters. It is well-structured with a clear breakdown. The parameter list adds length but is necessary given the schema's lack of descriptions. No unnecessary fluff.

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?

The description covers the parameters but omits critical context: how to obtain a valid URI, what happens if the track index is invalid, whether the tool replaces existing devices, and what the output schema contains (if anything). The presence of an output schema suggests a result, but the description doesn't hint at it. It also doesn't mention any prerequisites like a loaded session or selected track. Given the complexity of loading devices, this is incomplete.

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 no descriptions (0% coverage), so the description takes on the role of explaining each parameter. It provides a clear explanation for track_index and uri, with a concrete URI example, and explains that user_prompt is for telemetry. This adequately compensates for the schema's lack of detail, though it could go further with URI handling or track requirements.

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 states exactly what the tool does: 'Load an instrument or effect onto a track using its URI.' It clearly distinguishes from sibling load_drum_kit by covering both instruments and effects, and from browsing tools by focusing on loading onto a track. The verb 'load' and resource 'track' are specific.

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. It does not mention that it is the general loader and load_drum_kit is for drum kits specifically, nor does it explain any preconditions like having a track selected or a valid URI from the browser. The agent is left to infer usage 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.