itunes_play_song

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds the nuance that it plays the 'first matching track,' which is a useful behavioral trait beyond the name. However, it does not disclose side effects (e.g., whether it stops current playback), error handling, or prerequisites such as device selection.

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 extremely concise: two sentences totaling 16 words, front-loaded with the main action and followed by a key behavioral detail. Every sentence adds value; there is no fluff 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 tool with one parameter, no output schema, and no annotations, the description covers the essential semantics: what it does (searches and plays), the parameter meaning, and a critical behavioral detail (first match). It does not cover error or edge cases, but given the tool's simplicity and the absence of richer schemas, it is sufficiently complete.

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?

The schema provides no description for the single parameter 'song' (0% coverage), so the description must clarify its meaning. It does so by stating 'a specific song by name,' indicating that the song parameter is a song title. This is clear, though it could specify acceptable formats (e.g., with or without artist).

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: 'Search for and play a specific song by name.' It specifies the verb (search and play) and the resource (a specific song), and adds a distinctive behavior ('Plays the first matching track found in the library'), which helps differentiate it from related tools like itunes_search or itunes_play alone.

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 offers no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it, nor does it reference sibling tools like itunes_search, itunes_play, or itunes_current_track. The use case is only implied, not stated.

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