itunes_favorite_track

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

With no annotations provided, the description carries the full disclosure burden. It does clarify the toggle behavior (True to favorite/love, False to unfavorite) and implies a state dependency on the currently playing track. However, it doesn't disclose what happens when no track is playing, whether the operation is idempotent, or any error/edge-case behavior.

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 two sentences in a clean, front-loaded docstring format. Every word serves a purpose. The Args section is concise and directly follows the one-line summary. 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 tool with a single boolean parameter, no output schema, and no nested objects, the description covers the essential semantics. However, given the tool's dependency on mutable global state ('currently playing track') and the presence of 70+ siblings, a note about edge cases (e.g., nothing playing, or distinguishing from itunes_favorite_song) would push this to 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?

Despite having 0% schema description coverage, the description fully compensates by explicitly explaining the meaning of both the True and False values of the 'favorited' boolean ('True to favorite/love the track, False to unfavorite'). This is exactly the semantic information an agent needs beyond the bare 'boolean' type in the schema, and it's communicated unambiguously.

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+resource pair ('Favorite or unfavorite the currently playing track') that clearly states the action and scope. It clearly differentiates from most siblings like itunes_rate_track and itunes_dislike_track, though it doesn't distinguish itself from the near-identical itunes_favorite_song sibling.

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?

No when-to-use guidance, prerequisites, or alternatives are mentioned. Given the existence of itunes_favorite_song in the sibling list, explicit guidance on when to use which would be valuable. The description assumes the agent knows when this tool is appropriate.

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