load_instrument_or_effect

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

With no annotations, the description must disclose behavioral traits. It simply states 'load' without mentioning whether the operation replaces existing devices, what happens on invalid track indices, or whether it is destructive. This is insufficient for a mutation-capable 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 compact and well-structured, with the main action stated first and a clear parameter list. It contains no redundant content and is easy to parse.

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?

As a write operation with no annotations or output schema, the description fails to explain the operation's effects, prerequisites, or relationship to similar load tools. The URI example provides some context but is insufficient for reliable invocation.

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 description provides brief parameter explanations that the schema lacks, including a concrete URI example. However, it does not specify constraints, validation rules, or the full URI format beyond the example.

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 clearly states the tool loads an instrument or effect onto a track using its URI. It names a specific verb and resource, but does not explicitly distinguish it from similar sibling tools like load_item_to_track or load_drum_kit.

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 is provided on when to use this tool versus alternatives such as load_item_to_track or load_drum_kit. The description only states the basic operation without any context on selection criteria or exclusions.

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