piano_roll_humanize

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

With no annotations, the description carries the full burden of behavioral disclosure, but 'Add subtle timing+velocity randomisation' only implies mutation. It does not say whether notes are modified in place, whether randomisation is bounded by the jitter values, whether the operation can be undone, or what happens to existing timing/velocity data.

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 front-loaded sentence with zero filler; it is genuinely concise. However, it achieves conciseness by omitting important operational context, so it is structured efficiently but not optimally informative.

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 tool is simple with only two optional parameters and no output schema, yet critical context is missing: what notes are affected, how jitter values map to real timing/velocity changes, whether the operation is destructive, and whether a selection is required. The description is not sufficient for an agent to confidently invoke this tool correctly.

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, but it only repeats the high-level 'timing+velocity' concept. It never maps velocity_jitter to velocity randomization or timing_jitter_bars to timing randomization, nor does it clarify units, value ranges, or the meaning of the defaults.

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 a clear verb-resource pair: 'Add subtle timing+velocity randomisation.' This conveys a distinct humanize function and differentiates it from related piano roll operations like quantize or transpose, though it never states whether it applies to selected notes or the entire pattern.

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?

There is no guidance on when to use this tool, what to check before calling it, or which alternatives might be more appropriate. The word 'subtle' suggests a humanizing use case, but the description leaves the selection context and relationship to quantize/undo entirely implicit.

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