load_external_plugin

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

With no annotations, the description carries the transparency burden. It does disclose useful matching behavior: exact_match requires an exact normalized name match, and refresh_cache forces a rescan before matching. However, it does not describe error behavior, what happens if the plugin is not found, whether the plugin replaces existing devices, or whether the operation is undoable.

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: a one-sentence purpose followed by a clean parameter list. No filler or redundant content; every line provides useful 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?

The description covers the tool's purpose and all parameter semantics, and an output schema exists so return-value details are not required. It could be more complete by mentioning prerequisites or failure modes, but for invoking the tool correctly it is largely sufficient.

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%, but the description fully compensates by explaining all four parameters: track_index is 1-based, plugin_name includes an example, exact_match controls normalized matching, and refresh_cache forces a rescan. This adds meaningful semantics beyond the raw schema.

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 external plugin onto a track by plugin name, with the distinguishing note that no URI is required. This differentiates it from sibling tools like load_instrument_or_effect and 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?

The phrase 'by plugin name (no URI required)' implies the intended use case: when the agent has a plugin name rather than a URI. However, it does not explicitly mention alternatives or state when not to use this tool, such as when loading an instrument/effect by URI or when needing to browse available plugins.

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