load_zyn_preset

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

No annotations are provided, so the description carries full behavioral burden. It does disclose the track prerequisite and supported preset reference formats, but it does not mention what happens to existing settings, failure behavior for invalid tracks, or whether the operation overwrites the current preset. The description is adequate but not deeply transparent.

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 front-loaded with the core action, followed by the key prerequisite and parameter details. There is minor redundancy between the prose explanation of preset reference formats and the Args section, but overall it is well-organized and without significant fluff.

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 simple two-parameter tool, the description covers the essential call context: what the tool does, the required track instrument, and accepted preset formats. It does not explain error cases or return values, but an output schema exists, so return-value documentation is less critical. A brief pointer to list_zyn_presets for discovering valid preset names would improve completeness further.

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%, and the description compensates by defining both parameters: track_index as the target track index and preset as a name, 'Category/Name', or absolute path. This gives the agent meaningful guidance beyond the bare schema field names, though it could further specify indexing details.

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 states a specific verb ('Load'), a concrete resource (ZynAddSubFX preset .xiz), and the target (a zynaddsubfx instrument track). It clearly distinguishes itself from sibling tools like load_project and set_zyn_params by focusing on preset loading into a specific track type.

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?

It provides clear context: the target track must use the 'zynaddsubfx' instrument, and presets can be referenced by filename, 'Category/Name', or full path. It does not explicitly name alternative tools for related tasks like listing presets or adjusting parameters, but the usage context is sufficiently clear.

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