Adjust the pitch of any audio item by semitones (including fractional values) in a REAPER project to correct or creatively modify its tone.
Adjust the pitch of an audio item by semitones (can be fractional).
| Name | Required | Description | Default |
|---|---|---|---|
| semitones | Yes | ||
| item_index | Yes | ||
| track_index | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden but provides no behavioral details beyond the action. It does not state whether the modification is destructive, permanent, or requires selection.
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 is highly concise and front-loaded with the main purpose.
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 the simple tool, the description is too brief. It lacks information about return values, side effects, and requirements (e.g., track/item must exist). No output schema to compensate.
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 description must compensate. It adds context for 'semitones' (can be fractional) but provides no meaning for 'track_index' or 'item_index'. Partial compensation.
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 the action (adjust), the resource (pitch of an audio item), and the parameter (semitones, can be fractional). It distinguishes from sibling tools like adjust_playback_rate which adjusts pitch via speed.
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?
No guidance on when to use this tool vs alternatives like adjust_playback_rate or add_fx. No prerequisites or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.