set_scale

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

Annotations already declare a non-readOnly, non-destructive, non-open-world mutation, so the safety profile is covered. The description adds real value beyond that by disclosing the Scale Mode side effect (MIDI editor highlighting), but it does not say whether existing clips/notes are retuned or whether the change persists across the session.

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, zero padding, with the core action front-loaded and the interop note second. Slightly awkward phrasing ('Set the Set's key') costs it a point but nothing is redundant.

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 simple two-parameter mutation with no output schema and adequate annotations, the description covers purpose, concrete example, side effect, and interaction with sibling generators. Only the effect on pre-existing clip content is left unstated.

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 0%: 'root' is a bare string and only 'scale' has an enum. The example 'root "A"' gives the essential note-name format, which is the main gap filled, but accepted variants (sharps/flats, enharmonics, octave numbers) remain unstated.

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 gives a specific verb and resource — 'Set the Set's key' — and concretizes it with an example (root 'A', scale 'Minor'), plus the non-obvious effect of enabling Scale Mode. It is clearly distinct from siblings like set_tempo or set_label, though the noun 'Set' (Ableton Live Set) is jargon an agent must infer.

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?

It explicitly explains downstream usage: create_bassline and create_chord_progression pick up this key when root and scale are omitted, which tells an agent to call this first in a composition workflow. It stops short of stating when not to call it or whether re-calling overrides prior state.

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