Read a mix

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

Annotations already mark the operation readOnlyHint=true, so no safety disclosure is needed. The description adds useful behavioral context beyond that: it fetches a single revision and renders a compact text representation rather than raw JSON, which helps the agent anticipate output size and format.

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?

Two sentences with no filler: the first states what the tool does and the output form, the second states when to use it. Everything earns its place.

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?

For a read-only tool with a fully documented schema, the description provides the essential context: it fetches one revision, what data is rendered, and the intended workflow position. Without an output schema, the concise mention of 'compact text' plus the listed musical elements is sufficient guidance.

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 100%, so the schema already documents revisionId and raw fully. The description adds no new parameter-level meaning beyond restating output fields, matching the baseline for a fully covered 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?

The description uses a specific verb ('Fetches') and resource ('one revision') and enumerates the rendered elements: tracks, levels, panning, effects, and regions. It also distinguishes itself from siblings like bandlab_list_revisions and bandlab_edit_mix by scoping to a single revision for read-before-edit purposes.

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?

'This is what you read before proposing an edit' gives clear situational context and implies the tool should precede bandlab_edit_mix. It does not enumerate exclusions or alternatives by name, but the intended workflow is evident.

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