get_live_scale_reference

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description echoes 'Read-only.' It adds the specific output categories but does not disclose failure behavior, such as handling of invalid scale names, or whether results are cached. With annotations covering the safety profile, the description adds some value but not comprehensive behavioral context.

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?

A single sentence that gets straight to the point, front-loading the action and listing outputs without filler. Every word 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 two-parameter read-only lookup with no output schema, the description adequately states what it returns (intervals, pitch classes, note names, degrees, scale family). It does not mention error handling or the exact structure of the response, but given the simplicity, it is reasonably complete.

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 100%—both scaleName and rootNote have descriptive text ('Exact Live scale name' and 'C=0 through B=11'). The description reinforces 'exact' but does not add new syntax or format details. It meets the baseline for high schema coverage.

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 states a specific verb 'Resolve' with a clear resource ('one exact Ableton Live 12 scale and root') and enumerates the output categories (semitone intervals, pitch classes, note names, degrees, scale family). This distinguishes it from siblings like list_live_scales or analyze_midi_clip_scale, which have different 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?

The description implies its use for looking up a known scale's musical details, but it does not explicitly contrast with alternatives or state when not to use it. There is no mention of other tools like list_live_scales for enumeration, so guidance is implicit rather than explicit.

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