set_zyn_params

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose a key behavior: 'Only provided parameters are changed,' and it states the 0-127 value range. However, it does not describe mutation effects, error behavior, or what happens if the track is not a ZynAddSubFX track.

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 well-structured and efficient: a one-sentence purpose, two crucial usage constraints, then a clean parameter list. Nothing is redundant, and the front-loaded purpose makes orientation immediate.

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 an 8-parameter mutation tool with no annotations, the description covers the core requirements: target resource, parameter meaning, value range, and partial-update semantics. It could be more explicit about what 'global parameters' means versus per-note parameters, but the provided information 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%, so the description must compensate. It enumerates all eight parameters with human-readable meanings and value ranges, e.g., 'filterfreq: Filter cutoff frequency (0-127)' and 'track_index: Index of the zynaddsubfx track.' This adds meaning beyond the bare schema titles.

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 opens with a specific verb and resource: 'Set ZynAddSubFX global parameters on a zynaddsubfx track.' This clearly distinguishes the tool from siblings like set_track_volume and load_zyn_preset, and the parameter list makes the scope explicit.

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 description provides no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. Usage context is only implied by the tool's purpose; there is no explicit 'use when...' statement.

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