load_from_library

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

Annotations only declare readOnly=false, openWorld=false, destructive=false, so the description carries most of the load — and it does disclose the key side effect (loading an instrument replaces the track's current instrument) plus the recovery path (undo_last restores it), as well as the return values and how device_index feeds into read_device. It stops short of saying what happens on an invalid or non-loadable path, and the 'replaces current instrument' behavior sits slightly uneasily beside destructiveHint=false, though undo makes that defensible.

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 load action and its precondition come first, the return shape follows, and the sibling escape hatch is last — each sentence adds information with no filler or restatement of the name.

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?

There is no output schema, so the description rightly spends a sentence explaining the returned device names and device_index and how to consume it. Combined with the disclosed replacement/undo behavior, an agent has enough to call it correctly; only failure modes and the track parameter's exact meaning are unaddressed.

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 coverage is 0%, so the description must compensate, and it does for two of three parameters: root gets a concrete example ("drums") and path gets a constraint (must terminate at a loadable item) rather than just its type. The track parameter is only implied as the destination and is never explained (index base, expected track identity), leaving one real gap.

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 names a specific verb and resource — "Load a browser item onto a track" — and immediately anchors it with a concrete example (a drum kit from root "drums"). It also explicitly distinguishes itself from load_instrument, so an agent can separate the two tools without opening either schema.

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 hard precondition (path must end at an item that browse_library marked is_loadable), which routes the agent to browse_library first, and it names the alternative for instruments/presets (load_instrument). When-to-use, prerequisites, and the competing tool are all covered.

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