piano_roll_humanize

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

No annotations provided, so description should disclose behavioral traits. It mentions 'subtle' but does not explain whether it modifies notes destructively, which notes are affected (selected or all), or if results are reversible via undo.

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?

Extremely concise single sentence, but at the expense of essential details. No structure or front-loading of key usage context.

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 annotations or output schema, and 4 undocumented parameters, the description provides insufficient context for an agent to decide when and how to use 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%. The description adds no parameter meaning beyond schema titles. Default values are in schema but not explained (e.g., what 0.02 bars means).

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?

Description clearly states it adds randomization to timing and velocity. It distinguishes from quantization (snapping to grid), but could be more specific about scope (e.g., applies to 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?

Implies use for humanizing quantized sequences, contrasting with 'piano_roll_quantize'. But no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives like manual note editing.

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