get_mixer

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description does add real value by specifying that volume is Live's 0.0-1.0 fader value with 0.85 = 0 dB and that volume_display gives dB, which is context not present in structured fields. It does not say whether values are a live snapshot or how grouped/track ordering is represented.

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 tight sentences, front-loaded with the returned fields, with the unit-conversion caveat second. No filler, though the field list is a dense clause that reads slightly like a data dump.

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?

An output schema exists, so return structure need not be spelled out, and the annotations cover the safety profile. What remains unaddressed is scope nuance an agent would care about: whether all track types and groups are included, whether this reflects current live state, and how it relates to set_mixer.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. The volume-scaling note describes return-value semantics rather than parameters, which is useful but sits outside this dimension's remit.

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 concrete resource and enumerates exactly what is returned (volume, pan, mute, solo, arm, sends, colour, device names) across every track, return and master. That is a specific read operation, though it never names set_mixer or get_track_info as the contrasting siblings.

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?

There is no explicit when-to-use or when-not statement; the agent must infer that this is the read counterpart to set_mixer and the whole-console alternative to get_track_info. Usage is inferable from the scope wording but never stated.

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