live12_clip_transform_midi

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

No annotations are provided, so the description carries the full disclosure burden, and it is a mutation of clip note data. It never says whether the change is in-place and destructive to the original notes, whether it can be undone, whether it appends versus replaces, or what it returns. For a write operation with zero annotation coverage this is a significant gap.

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?

Single sentence, front-loaded with the action, with the algorithm list inline rather than as a separate block. No filler. Slightly dense but every clause names a real transformation the tool supports.

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 schema fully covers the four parameters including the nested params object, and no output schema exists, so return values need not be described. However, for a destructive note-transformation tool with no annotations, missing preconditions (MIDI clip requirement, target must have notes) and missing post-state information leave real gaps.

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 100% and the params object already documents per-transformation keys with examples, so the schema does the heavy lifting. The description adds a little by naming which transformations pair with which behavior (e.g. humanize covers both timing and velocity), but contributes no syntax or constraint detail beyond the schema. Baseline 3 is appropriate.

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 (applies algorithmic MIDI transformations) and enumerates the five concrete algorithms (humanize, velocity ramp, Euclidean, arpeggiation, pitch quantization). An agent can tell this is a note-content transformer rather than a transport/device tool. It stops short of distinguishing itself from near-siblings like live12_clip_quantize or live12_clip_modify_notes, which overlap in the note-editing space.

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?

Usage is only implied: apply one of the listed transformations to a MIDI clip identified by track/slot. There is no explicit 'use this instead of X' routing versus live12_clip_quantize (timing grid) or live12_clip_modify_notes, even though quantize_pitch/fit_to_scale overlap conceptually with both. No preconditions (clip must be MIDI, must contain notes) are stated.

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