load_instrument_or_effect

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

With no annotations, the description must fully disclose behavioral traits. It does not state whether loading replaces existing devices, if it requires an existing track, or any side effects. The only additional behavioral clue is the URI format example.

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?

Concise and front-loaded with the action. Two sentences plus a clean parameter list. No extraneous information.

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?

Tool has output schema, so return values are handled elsewhere. However, missing context about prerequisites (track must exist) and side effects (replaces existing device?). Adequate for a simple tool but not fully 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 0%, so the description must compensate. It provides explanations for both parameters: track_index (track index) and uri (URI with example). This adds meaning beyond the schema, though more detail on URI formats or track_index range would be beneficial.

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: loading an instrument or effect onto a track using a URI. The verb 'Load' and resource 'instrument or effect' are specific. Differentiates from siblings like 'load_sample_to_drum_pad' and 'load_drum_kit' by covering general instruments/effects.

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 on when to use this tool versus alternatives (e.g., 'load_sample_to_drum_pad' or 'load_drum_kit'). Does not mention prerequisites or contexts where this tool is appropriate.

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