plugin_set_vst_state

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

No annotations, so description must disclose behavior. Mentions 'in-memory Edit' and 'existing plugin', indicating mutation of in-memory session and requirement for existing plugin. However, doesn't describe side effects like overwriting, error conditions, or whether it's undoable. Missing details about compatibility of state blob with target plugin type.

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 sentences, front-loaded with action and source, no unnecessary words. Efficiently conveys purpose and use case.

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 3-param mutation tool with no output schema, the description omits return behavior, error conditions, and compatibility requirements. It references the capture tool but doesn't state that the plugin must be of the same type or that the state must match. Also doesn't mention whether the operation is destructive or reversible. Incomplete for an agent to call confidently.

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 description must explain params. It explains that 'state' is a base64 VST state blob from plugin_state_capture, but does not explain track_id and plugin_id. These are likely identifiers but not elaborated. The description adds some value for state but insufficient for the other two.

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 'Apply' and resource 'base64 VST state blob' to an existing plugin. Mentions source (plugin_state_capture) and use case (copy onto every other instance), clearly distinguishing from plugin_set_param and plugin_state_capture.

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 the workflow of capturing then applying, and says it's for copying configurations across instances. Doesn't explicitly mention when not to use, but the reference to plugin_state_capture and the phrase 'copy one configured VST' gives enough context to infer.

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