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

No annotations provided, but description explains the operation (adds per-note cent offsets), return values (per-track counts, total detuned, cent range), and parameter effects. Lacks explicit statement on reversibility or side effects, but is fairly transparent.

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?

Contains two paragraphs plus a bullet list and an example. Every sentence adds value, no fluff. Front-loaded with purpose and usage, then parameter details, then example.

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?

Complete for a tool with 6 parameters, no annotations, and an output schema. Covers purpose, usage guidelines, parameter semantics, and return value. Includes examples and distinguishes from sibling.

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?

With 0% schema coverage, description fully documents each parameter: unit_index, track_index, region_index with -1 meanings; cents_depth with qualitative examples; bias direction; seed for reproducibility. Adds significant meaning beyond schema.

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?

Clearly states it adds micro-detune (cents) to notes for intonation humanization. Distinguishes from sibling humanize_notes which handles velocity/timing/duration but not pitch.

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?

Explicitly contrasts with humanize_notes and provides specific use cases (string sections, vocal MIDI, brass, sterile MIDI). Tells when to use and when not.

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