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

With no annotations, the description carries the full burden. It explains the pipeline (parse WAV, auto-detect BPM, transcribe drums with pitch mappings, transcribe melody, create notes via batch), and documents return values, making its behavior highly 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?

Well-structured with summary, pipeline, use cases, parameters, returns, and example. Every section earns its place, and the key purpose is front-loaded.

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?

Despite being a composite tool, the description covers purpose, pipeline, parameters, return values, and examples. There is no output schema provided, so the explicit return list is valuable, and no gaps remain for correct invocation.

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%, so the description fully compensates by explaining every parameter: filename (exports dir or absolute path), bpm auto-detect, unit_index, drum_track, and melody_track defaults. It includes a concrete usage example.

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?

States exactly what it does: transcribes a full audio track (drums + melody) into MIDI notes in one call, and explicitly says it runs transcribe_drums + transcribe_melody, distinguishing it from those sibling tools.

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?

Clearly says it eliminates 2 separate calls and positions it in the Suno-to-MIDI pipeline, with concrete use cases. This gives strong guidance on when to use this composite tool versus the individual transcription tools.

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