itunes_favorite_song

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

The description indicates a mutating action (favorite/unfavorite) and clarifies the effect of the 'favorited' parameter. It does not mention potential side effects or errors, but for a simple toggle it is sufficiently transparent.

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, using two short sentences with no redundant information. It is well-structured and directly addresses the tool's function without unnecessary detail.

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?

Given the tool's simplicity and lack of output schema, the description is complete enough for a straightforward action. It could benefit from noting that the operation searches by title, but that is already implied. Overall, it provides sufficient context for a simple 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?

The description adds meaning to the parameters: 'song' is identified as a title, and 'favorited' is implied to control the favorite/unfavorite action. This supplements the schema, which only provides types and names, making the parameters' roles clearer.

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: favoring or unfavoriting a song by title. It specifies the exact action and target object, leaving no ambiguity about the tool's purpose.

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 lacks guidance on when to use this tool compared to other iTunes tools (e.g., favorite_track, favorite_album). It does not mention prerequisites, edge cases, or alternative approaches, so users may not know when this is the appropriate choice.

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