sync_liked_songs

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

With no annotations, the description bears full burden for behavioral disclosure. It only states the basic action, omitting details on whether it creates or updates records, if it requires authentication, or if it modifies remote data. The word 'sync' implies data transfer but no safety or side effects are described.

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 short but lacks necessary details. It is under-specified rather than concise. A concise description would still convey essential parameters and usage context.

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 has one parameter, no output schema, and no annotations, the description is incomplete. It does not explain what sync does, how limit affects behavior, what the return value is, or error conditions. The sibling tools suggest related operations but no cross-references.

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 coverage is 0% and the description provides zero information about the single parameter 'limit'. The agent cannot infer its purpose (e.g., number of songs to sync) from the tool description alone.

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 'Sync liked songs into local SQLite' clearly states the action (sync) and resource (liked songs, local SQLite). It distinguishes from sibling 'list_liked_songs' which only retrieves. However, the verb 'sync' is somewhat ambiguous without specifying directionality or whether it's incremental.

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 guidance on when to use this tool versus alternatives like 'list_liked_songs' or 'enrich_tracks'. The description does not mention prerequisites, expected state, or scenarios where sync is appropriate.

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