load_from_browser

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

With annotations covering the safety profile (destructive=true, idempotent=false), the description adds substantial behavior: an instrument/preset/drum kit replaces the track's instrument, a sample on a MIDI track becomes a Simpler, clips load as a new track, and the default slot is the first empty slot. It discloses exactly what gets mutated, which is what an agent needs for a destructive 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?

Front-loads the core action and packs target-specific semantics into a tight block with no filler. Slightly hurt by mid-sentence line breaks that make the 'Targets' paragraph denser to parse than necessary.

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 7-parameter tool with no output schema, it covers the selector inputs, the target rules, edge cases (clips create tracks), defaults, and even the return shape. Nothing material an agent needs to call it correctly is missing.

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 carry the full burden, and it largely does: position (device insert index), drum_pad (note 'C1'/36 or pad name), slot (Session scene index, default first empty), and the uri/path/query disjunction are all clarified beyond the bare types. Only 'track' is left to inference, keeping it just below full compensation.

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?

States a specific verb (Load) and resource (browser item onto a track) and names the sibling tools (search_browser, browse) that produce the identifier. An agent can distinguish it from add_device/add_* siblings without opening any 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?

Explicitly requires exactly one of uri/path/query and points to search_browser/browse as the source for identifiers, giving clear workflow context. It stops short of contrasting directly with add_device (the nearest sibling for placing devices), so it is clear but not fully alternative-routing.

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