Write piano-roll notes

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

The description adds significant context beyond annotations by detailing quantize grid snapping and the need for a specific setup step. It confirms destructive behavior (mode='replace' clears first). Could mention error conditions if the piano roll isn't open, but overall strong.

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 (4 sentences) and front-loaded with the main action, followed by parameter details and setup. Every sentence adds value with no redundancy.

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?

The description covers setup, note format, quantize, and mode. It doesn't explain output or error handling, but an output schema exists. For a tool with 3 parameters and 1 required, this is fairly complete.

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?

The description adds meaning beyond the schema by explaining the note structure in plain language and providing concrete quantize values ('0.0625=1/16, 0.125=1/8, 0=off'). With 67% schema coverage, the description compensates well.

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's purpose with a specific verb-resource combination: 'Write notes into the currently-open FL Piano roll.' It distinguishes itself from sibling tools like fl_write_raga_chords and fl_write_raga_melody by targeting piano roll 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 explicit setup instructions ('open the Piano roll and run 'MCP_Apply' once') and explains the mode parameter's behavior. While it doesn't explicitly state when not to use this tool, the context is clear and useful.

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