rediscover

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

The description discloses useful filtered behavior: it surfaces liked songs from years ago that are missing from top tracks or recent plays. With no annotations, the burden is fully on the text, but it does not state whether the tool is read-only, modifies anything, or how the rediscovered songs are presented.

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 short and front-loaded with the core idea: old liked songs absent from recent activity. The phrase 'forgotten favourites, spread across artists' is somewhat emotive and not strictly necessary, which keeps it from a perfect conciseness score.

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?

With no annotations, no output schema, and limited parameter description, more operational detail is needed. The text gives a good conceptual summary but does not clarify what the tool returns, whether it mutates anything, or how to relate the result to sibling operations like playlists and saved tracks.

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 responsibility falls on the description. Only 'years ago' loosely hints at min_years_ago, and the limit parameter is not mentioned at all in prose. The description does not compensate for the absent schema-level documentation.

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 identifies what the tool surfaces: old liked songs that no longer appear in top tracks or recent plays. The exclusion condition helps distinguish it from tools like get_saved_tracks, get_top_tracks, and get_recently_played. However, it lacks an explicit verb such as 'retrieves' or 'returns,' relying on the tool name for the action.

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 implies when to use it: for forgotten favorites from past years that are absent from current top/recent activity. It does not name alternatives, state when not to use it, or explain how it complements the sibling tools, so the guidance is more contextual than explicit.

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