spotify_sync_library

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

With no annotations, the description carries the full burden. It discloses what data is synced (liked songs, user-created playlists) and what is skipped (followed/saved playlists by others). It also explains the force parameter for re-syncing. It does not detail incremental updates or index management, but the core behavior is clear.

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 very concise: a one-sentence purpose, a brief note on what is synced, a usage hint, and a three-line parameter list. Every sentence adds value with no 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?

Given the existence of an output schema (not shown), it does not need to detail return values. It covers purpose, data scope, and parameters. It could mention post-sync querying possibilities, but overall it is adequate for a sync 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?

Schema description coverage is 0%, so the description must compensate. It provides an 'Args' section that explains each parameter's purpose and default values (include_liked, include_playlists, force), adding significant semantic meaning beyond the bare schema.

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 syncs the user's Spotify library to a local index for AI-powered curation. It specifies it fetches liked songs and tracks from user-created playlists, and explicitly skips followed/saved playlists by others, differentiating it from many sibling tools that manipulate or query playlists.

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?

It suggests periodic usage ('Run periodically to keep fresh') but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. The context is implied but not explicit.

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