voice_notes_to_piano_roll

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

No annotations are provided, so the description carries full burden. It discloses that the tool is pure-Python and does not require audio extras, which is useful. However, it omits behavioral traits like whether it overwrites existing piano roll content (though the 'clear_first' parameter defaults to true, it's not mentioned). More detail on side effects or prerequisites would improve transparency.

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 four sentences, front-loaded with the main purpose and optional features, followed by a use case and implementation note. Every sentence adds value, and there is no redundancy or filler.

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 tool has 7 parameters (1 required) and no output schema, the description provides a high-level purpose and context for usage but does not explain return values, error conditions, or detailed parameter interactions. It is adequate for selection but not for full invocation understanding.

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 compensate. It mentions 'scale snapping, transposition, quantize' which correspond to some parameters (scale/scale_root, transpose_semitones, quantize_grid_sec), adding meaning. However, it does not describe the required 'notes' parameter format, 'bpm', or 'clear_first' behavior, leaving significant gaps.

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 tool 'push[es] an already-transcribed note list into the piano roll', specifying the verb and resource. It distinguishes itself from siblings (like voice_to_piano_roll) by emphasizing that it works with pre-transcribed notes and offers optional transformations.

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 a clear use case: 'when you want Claude to inspect the raw transcription first, tweak it, then send a cleaned-up version.' It also references the source tool (voice_record_and_transcribe). However, it does not explicitly mention when not to use this tool or name alternatives.

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