ramp_midi_note_velocities

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

Beyond the single destructiveHint false annotation, the description discloses several behavioral specifics: interpolation is by onset, chords get same velocity, results clamp to 1-127, and out-of-range velocities clamp rather than error. This adds real value. However, it omits any mention of return behavior (despite a return_notes parameter) and the filtering mechanism, which are relevant side effects.

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 concise and well-structured. It leads with the purpose, follows with a clear algorithm explanation, and lists the two key parameters with annotations. No redundant information; every sentence contributes to understanding the core behavior.

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?

Given 11 parameters, no output schema, and minimal annotations, the description is incomplete. It does not explain how the filtered note set is determined (the role of track_index, item_index, channel, pitch, beat filters) nor what the tool returns (return_notes). This leaves critical usage knowledge missing, especially for a tool with such a large parameter 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 0%, so the description must explain parameters. It only covers start_velocity and end_velocity (including clamping behavior), but leaves the other 9 parameters (track_index, item_index, fields, channel, pitch_low/high, start_beat/end_beat, return_notes) entirely unexplained. The agent must guess their meaning from names alone, which is insufficient for correct invocation.

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 clearly states a specific operation: applying a linear velocity ramp (crescendo/decrescendo) across MIDI notes. It uses a precise verb and resource, and the interpolation details (by onset, linear, chords share velocity) make the purpose unmistakable and distinct from sibling tools like scale_midi_note_velocities or humanize_midi_notes.

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. It does not mention conditions (e.g., 'when you need a gradual dynamic change') or exclusions ('do not use for uniform scaling'). It only describes what the tool does, leaving the agent to infer applicability from context.

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