get_track_volume

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

No annotations exist, so the description bears the full disclosure burden. It conveys the unit (dB), which is genuinely useful, but says nothing about read-only semantics, what happens with an out-of-range trackIndex, or whether the track must exist in the active sequence.

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?

A single tight fragment with the resource and unit front-loaded and no filler. It is under-specified rather than verbose, which is not penalized here.

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 one-parameter getter with full schema coverage this is close to adequate, but with no output schema the description should state what is returned (a numeric dB value, and silence/-inf at the low end). That return-shape gap is the main omission.

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?

Single parameter with 100% schema coverage, including the helpful 'V1 = 0, A1 = 0' indexing note. The description adds nothing beyond the schema, which is the expected baseline when the schema is self-documenting.

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?

Names a specific resource – the Audio Track Mixer fader level of a track – and states the unit (dB), which distinguishes it from get_clip_volume and get_track_info. The verb is only implicit in the tool name; the description itself never says 'get' or 'return'.

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?

No guidance on when to call this versus the sibling set_track_volume, get_track_info, or get_clip_volume. An agent must infer from the name that this is the read counterpart to set_track_volume.

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