piano_roll_quantize

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

No annotations exist, so the description must disclose behavioral traits. It states 'snap' implying modification, but doesn't clarify if it's destructive, what happens to original positions, or if it affects all notes or only selected ones.

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?

While short, the description is too terse and fails to earn its place—it omits essential details, forcing agents to guess or rely on external knowledge. Conciseness without completeness is insufficient.

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?

With no output schema, no annotations, and 4 undocumented parameters, this single-sentence description is grossly incomplete. Agents cannot safely or effectively use this tool based solely on the definition.

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 coverage is 0% and the description explains zero parameters. Agents cannot infer the meaning of grid_bars, strength, channel, or pattern from the description, leaving them blind to crucial configuration.

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 'Snap existing notes to a grid' clearly indicates the tool quantizes notes. However, it could be more specific about the scope (e.g., piano roll notes) and the meaning of 'grid'. It distinguishes from siblings like piano_roll_humanize.

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 no guidance on when to use this tool versus alternatives like channel_quick_quantize, nor any prerequisites (e.g., must select notes first). Agents lack context for proper invocation.

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