live12_device_set_parameter

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the tool mutates a live parameter and accepts normalized inputs, but it does not state whether changes are immediate, reversible, require devices to exist, how out-of-range values are handled, or what errors occur on invalid indices.

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 tightly written sentences with zero waste, front-loading the core action and following with the key behavioral nuance. Every sentence 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 mutation tool with five parameters, no annotations, and no output schema, the description is too thin. It covers purpose but omits return values, error behavior, index resolution rules, and mutation side effects, leaving an agent under-informed about safe 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 100%, so the schema already documents all five parameters in detail, including the normalized flag and parameter_identifier union. The description's mention of raw engineering values and normalized [0.0..1.0] inputs repeats schema semantics rather than adding new meaning, so the baseline 3 applies.

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 names a specific verb ('Sets') and resource ('device parameter in Ableton Live 12'), with a concrete API reference (DeviceParameter.value). It is clear what the tool does, but it does not distinguish itself from sibling setters like live12_lom_set or live12_rack_macro_control.

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 offers no guidance on when to use this tool versus alternatives such as live12_lom_set or live12_device_get_parameters. It only states capability ('Supports both raw engineering values and normalized inputs') without usage conditions or exclusions.

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