summarize_liked_library

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It does not mention whether the operation is read-only, what 'unavailable tracks' means, any performance implications, or the structure of the output. This is a significant gap for a tool that likely aggregates data.

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 a single, concise sentence that front-loads the main purpose. It is not verbose and every word contributes to the meaning. However, it is so brief that it omits essential details, which slightly reduces the efficiency of the communication.

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 complexity (summarizing multiple categories), the lack of output schema, and empty parameter descriptions, this description is highly incomplete. It leaves critical questions unanswered: What does the summary look like? How are 'unavailable tracks' determined? What is the effect of 'top' and 'limit'? An agent would struggle to predict the tool's behavior or interpret its response.

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%, and the description says nothing about the 'top' and 'limit' parameters. While their names hint at quantities, without explanation an agent cannot know if 'top' refers to top artists, top albums, or something else. The description fails to compensate for the empty 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 summarizes liked favorites, specifying dimensions: artists, albums, years, and unavailable tracks. This distinguishes it from sibling tools like list_liked_songs and export_liked_songs, which obviously list or export rather than summarize. It is a specific verb+resource combination.

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 is provided on when to use this tool versus alternatives. The description merely states what it does, without suggesting contexts or mentioning sibling tools. An agent would have to infer usage solely from the name and description, which is insufficient.

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