itunes_set_track_bpm

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

With no annotations provided, the description carries full burden. It discloses a key behavioral trait: if 'song' is empty, it modifies the currently playing track. This is essential for an agent to understand default behavior. It could further mention side effects like overwriting existing BPM, 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 concise and well-structured: a clear one-line purpose, followed by a neatly formatted 'Args:' section. Every sentence provides useful information without waste.

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 setter tool with 2 parameters and no output schema, the description covers the essential aspects: what it does, what parameters control, and the default behavior. It doesn't mention return values, but that's typically unnecessary for such a tool. It's sufficiently complete for an agent to use correctly.

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?

Despite only 0% schema description coverage, the description fully explains both parameters: 'bpm' with an example (120, 140) and 'song' with its optionality and default action. This adds significant meaning beyond the schema, which only provides types and defaults.

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 clearly states the tool's function: 'Set Beats Per Minute (BPM) tempo on a track.' The verb 'Set' plus the resource 'track' and attribute 'BPM' makes it specific. It distinguishes from siblings like itunes_edit_track_metadata by targeting a single attribute, and it also specifies the default behavior when song is empty.

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 description provides context by explaining the optional 'song' parameter and its fallback to the currently playing track. While it doesn't explicitly mention alternative tools, the targeted nature of the operation (setting BPM) makes its use case clear. There is no explicit exclusion, but the purpose is well-defined.

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