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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds real behavioral meaning for ducking (amount lowers music while speech occurs; null disables it), but says nothing about whether unspecified fields are left unchanged, whether a partial update is atomic, or what permissions/state are required.

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 dense sentence with the primary operations front-loaded and the non-obvious ducking semantics tucked into a parenthetical. No filler, though it omits one short clause (only supplied fields change) that would have cost little.

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?

With 7 parameters, 14% schema coverage and no output schema, the description covers the field semantics well but leaves gaps an agent would care about: partial-update behavior, whether ducking here conflicts with set_ducking, and any confirmation of what the call returns. Adequate but not complete for a mutation tool.

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 only 14%, so the description has to compensate, and it largely does: it maps name/muted/hidden/locked to their effects and explains the ambiguous anyOf duck parameter including the null branch, which the schema does not clarify. Only trackId and projectId are left to the schema, which is acceptable since projectId is already documented there.

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 verb set (rename/mute/hide/lock) against a clear resource (a track), and the parenthetical explains the ducking case. It stops short of differentiating from the sibling set_ducking, which also appears to touch ducking, so the boundary is not fully resolved.

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?

Usage is implied by the enumerated operations — an agent can map 'rename' to name and 'mute' to muted — but there is no explicit when-to-use or when-not guidance. Notably, nothing says when to use this tool's duck parameter versus the sibling set_ducking, and nothing points to move_track/remove_track for the operations this tool does not cover.

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