getUsersSavedTracks

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get a list', which implies read-only behavior, but it does not mention pagination, authentication, or what happens if there are no saved tracks. Minimal behavioral context is added beyond the verb itself.

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 sentence of 11 words, extremely concise and front-loaded with the action and object. It contains no filler, repetition, or unnecessary detail.

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 tool with two optional numeric parameters, the description is adequate but lacks behavioral nuances such as pagination behavior and output structure. Since there is no output schema and no annotations, additional context about the returned list or pagination would make it more complete.

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?

The input schema fully describes both parameters (limit and offset) with clear descriptions and constraints, achieving 100% schema description coverage. The description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 verb 'Get' and the specific resource 'tracks saved in the user's 'Liked Songs' library', which unambiguously distinguishes it from sibling tools like getAlbumTracks or getPlaylistTracks. It immediately conveys the tool's function without any ambiguity.

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 provides clear context by identifying the 'Liked Songs' library, making it easy to infer when this tool should be used instead of other track-retrieval tools. However, it does not explicitly mention exclusions or alternative tools, lacking the 'when-not' guidance that would push it to a 5.

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