get_saved_tracks

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

Annotations already declare readOnlyHint=true, so no safety warning is needed. The description adds meaningful behavioral context by clarifying that 'saved' means 'Liked Songs' and by specifying the sort order ('most recent first'), which helps the agent understand what to expect from the result list.

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?

A single, tightly written sentence that front-loads the core purpose and then supplies the key ordering detail. Every word adds value and there is 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?

For a simple read-only list operation, the description covers the resource, the user scope, the naming convention, and the ordering. Annotations cover safety, and an output schema exists, so return-value details are already structured. Nothing essential is missing.

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 should compensate for limit and offset. It does not explain those parameters, but the added 'most recent first' ordering implicitly defines what offset means relative to the list. Since limit and offset are conventional pagination parameters with defaults, the description is adequate but not enriching.

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 the resource ('Tracks saved to the user's library') and adds the useful label 'Liked Songs' to resolve naming ambiguity. It is distinguishable from siblings like get_saved_albums and get_recently_played, but it does not explicitly call out any sibling or contrast, so it falls just short of a 5.

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 context is clear: this is for listing a user's liked/saved tracks, sorted newest-first. There is no explicit guidance about when to prefer this over siblings such as get_recently_played or get_saved_albums, so usage guidance is implied rather than stated.

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