live12_scene_set_properties

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says 'configures' but does not state whether this is a partial update, whether omitted fields are preserved, or how tempo_enabled/time_signature_enabled interact with their associated value fields; for an 8-parameter mutation tool this is a meaningful gap.

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 a single, front-loaded sentence with no wasted words. It is concise but could have used the available space to clarify update semantics or the enabled/disabled flags.

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 no annotations, no output schema, and 8 parameters with conditionally relevant fields, the description is incomplete: it does not explain partial update behavior, required existing-scene context, or how the enabled flags gate tempo and time signature values. The schema covers parameter meaning, but the tool's behavioral contract remains under-specified.

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 all 8 parameters. The description lists the configurable dimensions but does not add constraints or coupling semantics beyond what the schema provides, such as why tempo_enabled exists alongside tempo.

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 ('Configures scene parameters in Ableton Live 12') and enumerates the configurable fields: name, color, tempo assignment, and time signature assignment. It is distinguishable from scene_create and scene_fire, but it does not explicitly differentiate itself from adjacent property-setting tools like live12_clip_set_properties or live12_track_set_properties.

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 does not explain when to use this tool versus scene_create, scene_fire, or transport-level tempo/time signature tools. It also omits prerequisites (e.g., that the scene_index must refer to an existing scene) and does not mention when to prefer this over direct LOM calls.

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