live_plugin_snapshot

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

No annotations exist, so the description carries the full burden; it does usefully disclose the storage location (studio-one-mcp data folder), the coverage limit (PreSonus plug-ins, all known parameters), and that restore only writes differing parameters. It is silent on what save does when the name already exists, whether slots are overwritten, and what error behavior looks like when a plug-in kind mismatches.

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?

Two dense sentences, front-loaded with the three actions and followed by the storage/coverage caveat. No filler, though the second sentence packs several distinct facts (location, plug-in scope, parameter naming reference, restore diffing) without structural separation.

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 multi-action, 5-parameter tool with no annotations and no output schema, the description covers save and restore reasonably but leaves the list action's return shape and the 'slot' parameter entirely unaddressed. Adequate for the main flow, incomplete for the full surface.

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 only 20% across 5 parameters. The description adds meaning for 'name' (snapshot label), 'plugin' (list filter), and implicitly 'channel' (any channel), but 'slot' is completely unexplained in both schema and description, and the save/restore vs. list distribution of parameters is not spelled out.

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?

Names three concrete actions (save, restore, list) on a concrete resource (a plug-in's settings) and frames the tool as a remote stand-in for presets, which is a clear purpose. It does not name any sibling (e.g. live_mix_snapshot or live_plugin_params) to distinguish against, so differentiation is left to inference.

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?

Implies usage via 'restore them onto the same kind of plug-in (any channel)' and the 'stand-in for presets' framing, plus the constraint that save/restore operate on raw parameter values for PreSonus plug-ins. There is no explicit when-to-use vs. live_mix_snapshot or live_plugin_params, and no exclusion or precondition stated for the list action.

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