set_midi_note_velocity

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

With no annotations, the description carries the full behavioral burden. It discloses the valid velocity range (1-127), which is genuinely useful, but says nothing about whether the target note must already exist, whether the change is undoable, or what happens on out-of-range input.

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 text is short and front-loads the purpose, but the 'Args:' block documents only one of four required parameters, so the brevity reflects under-specification rather than tight editing.

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 4-required-parameter mutation tool with no annotations, no output schema, and 0% schema coverage, the description leaves the addressing scheme (track/item/note indices) entirely unexplained and gives no return or error behavior.

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 three of the four parameters (track_index, item_index, note_index) are undocumented in both the schema and the description. The description compensates only for velocity by adding the 1-127 range, which the bare 'integer' schema type does not convey.

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 and resource ('Set the velocity of a MIDI note'), so the core action is unambiguous. It does not differentiate from adjacent siblings such as set_midi_note, ramp_midi_note_velocities, or scale_midi_note_velocities, which all operate on the same note data.

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?

There is no guidance on when to use this versus set_midi_note (which likely also sets velocity) or the ramp/scale velocity tools. No prerequisites or context are given.

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