get_mixer_panning_context

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuine context — that unsupported fields are reported explicitly rather than silently omitted, and that native owner/mixer/parameter identities are bound — but phrases like 'All profile' are opaque jargon that don't clearly disclose behavior.

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?

It is short and front-loads the read action, but several fragments ('Binds native owner/mixer/parameter identities,' 'All profile') cost more in ambiguity than they save in brevity. The sentences are dense staccato units that a reader must re-parse.

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 value shape need not be explained, and the description covers scope (Track/Group/Return/Main), the value families returned, and the explicit-unsupported-fields behavior. For a single-parameter read tool this is nearly sufficient, with 'All profile' the only loose end.

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?

With 100% schema description coverage on the single trackId parameter, the schema already explains accepted forms ('track-N from list_tracks, return-N from get_set_mixer, or master'). The description adds nothing about the parameter, 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?

Starts with a specific verb and resource: 'Read exact track, Group, Return or Main panning mode and Stereo/left/right native values, displays, bounds, enablement and automation,' which tells an agent exactly what data this returns. The 'Read' framing implicitly contrasts with the set_mixer_panning sibling, but no sibling is named, so differentiation is left to inference.

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 statement of when to use this versus get_track_mixer, get_set_mixer, or set_mixer_panning — the agent must infer from the name and the 'Read-only' phrase. No prerequisites or exclusions are given, so the nearest thing to guidance is the optional catch-all 'All profile.'

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