load_instrument_or_effect

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

Beyond the annotation 'destructiveHint: false', the description only states 'load' without disclosing whether it replaces existing devices, appends, or any other side effects. Minimal extra value.

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 with a clear header and bulleted parameters, no unnecessary words or repetition.

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?

For a simple load operation with an output schema (unseen), the description covers the basic action but omits error conditions and return values. Adequate but not 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?

With 0% schema coverage, the description lists parameters and gives a URI example but does not explain the track_index range or how to obtain valid URIs. Partially compensates but lacks depth.

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 uses a specific verb 'Load' and identifies the resource as 'instrument or effect onto a track', clearly distinguishing it from sibling tools that load to master or return tracks.

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 implies usage for loading onto a track but does not provide explicit guidance on when to use this tool versus alternatives like 'load_device_to_master', nor does it mention prerequisites such as valid track index or URI.

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