uad_load_plugin

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

With no annotations, the description carries the burden and discloses key behavioral details: polling up to 5 seconds, waiting for parameter nodes to materialize, and reporting whether they did. It also reveals the optional preset recall. Some side effects like power management are not mentioned, but the core behavior is transparent enough.

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 three sentences, front-loaded with the primary action, and every sentence adds value. No redundant or vague filler.

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 provides solid purpose, usage, and behavioral context, and an output schema exists for return values. However, with no annotations and zero schema descriptions, the unexplained target/device/power parameters leave notable gaps for a tool of this complexity.

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 schema has no descriptions (0% coverage), so the description must compensate. It explains slot values and preset usage, but leaves target, device, and power undefined. These are significant gaps for a 6-parameter tool with only 2 inferred parameter meanings.

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 a specific action: loading a UAD plugin into an insert slot or the Unison preamp slot, followed by polling for parameter nodes. It also distinguishes itself from sibling tools by explicitly mentioning what it is not for.

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?

Provides explicit 'Use when' guidance and names sibling alternatives for excluded use cases (uad_set_plugin_params, uad_remove_plugin). This is model guidance for tool selection.

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