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

No annotations provided, so description carries full burden. It details internal steps (auto-detect BPM, transcribe drums to specific pitches, transcribe melody with cents+clarity, create MIDI notes via create_notes_batch) and mentions returns. It lacks side-effect information 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?

The description is well-structured: a one-sentence summary, then composite explanation, pipeline steps, use cases, parameter list, and example. It is concise (no filler) and front-loaded with the most important information.

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?

Given the complexity (audio to MIDI with multiple tracks, BPM detection), the description covers key aspects: purpose, pipeline, use cases, parameters, and returns. It could mention file format constraints or performance notes, but it's largely complete for selection and 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%, but the description compensates by describing each parameter: filename (with path hint), bpm (default 0 meaning auto-detect), unit_index, drum_track, melody_track. It adds meaning beyond the bare schema, though could be more precise about filename format.

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 clearly states it transcribes a full audio track into MIDI notes, specifying drums and melody. It distinguishes itself by being a composite of transcribe_drums and transcribe_melody, which are listed as sibling tools, and explicitly says it eliminates two separate calls.

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 pipeline steps and use cases (e.g., Suno-to-MIDI pipeline, extract groove, convert loop), making it clear when to use. It implicitly contrasts with separate transcribe calls but doesn't explicitly say when not to use it.

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