piano_roll_transform

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the delete/clear operations add no new information beyond the safety profile. The description does not disclose additional behavioral context such as how the tool interacts with the current piano roll, the auto_trigger mechanism, or whether it can be undone. It adds no value over annotations and the schema's parameter descriptions.

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 a single clear sentence that front-loads the operation list and scope. Every word contributes for place zero filler. It is appropriately sized for a tool whose main purpose is simple though the underlying parameter space is complex.

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 multi-operation tool with a nested request schema, the description is too minimal. It does not explain which parameters apply to which operation, how the global channel_index/pattern_number context interacts with notes, or the role of the auto_trigger field. The output schema exists, so return values are covered, but an agent still lacks the operation–parameter mapping and scenario guidance to invoke the tool correctly without extensive manual schema exploration.

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?

With schema description coverage reported as 100%, the baseline is 3. The description lists operation names and the scope (selected/all) which mirrors the enum values already present in the schema, but does not explain how parameters like semitones, grid_beats, or repeats relate to each operation. No new semantic meaning is added beyond what the schema already provides.

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 names specific operations (quantize, transpose, humanize, duplicate, delete, clear) on a specific resource (notes) and the scope (selected/all). This clearly distinguishes it from siblings like piano_roll_read_notes and piano_roll_write_notes, so an agent can tell which tool to choose without opening the schema.

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 is given about when to use this tool versus alternatives, such as when to prefer it over piano_roll_write_notes or piano_roll_read_notes. The description provides no context about prerequisites, pattern/channel selection, or scenarios where this tool is the right choice, leaving the agent to infer usage from the operation list alone.

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