itunes_set_track_volume_adjustment

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

With no annotations, the description carries the burden of behavioral disclosure, and it does so well: it states the operation is a relative volume adjustment, constrains it to -100% to +100%, and explains the fallback behavior when song is empty ('modifies currently playing track'). It could mention error cases or persistence, but for a simple setter this is adequate.

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?

The description is compact, front-loaded with the core action, and includes a short Args section that earns its place by adding meaning beyond the bare schema. No filler or redundancy.

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 simple two-parameter setter with no annotations and no output schema, the description provides enough context: action, target, valid range, and optional song fallback. It stops short of covering edge cases like invalid track names or whether the change persists, but those are not essential for basic 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 description coverage is 0%, so the description must fully compensate. It explains both parameters: adjustment's valid range (-100 to 100 percent) and song's optionality plus default behavior. It even supplies range constraints that the input schema lacks (no minimum/maximum on adjustment).

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 uses a specific verb and resource: 'Set relative volume adjustment' for 'track gain normalization.' It clearly identifies what is modified and the -100% to +100% range, distinguishing it from sibling volume tools like itunes_set_volume and itunes_set_device_volume.

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 phrase 'for track gain normalization' and the optional song parameter give clear context about when to use this tool: to adjust a track's relative gain, either by title or on the currently playing track. It does not explicitly name alternatives or exclusions, but the intended use case is clear from the wording.

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