get_saved_tracks

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

With no annotations and no output schema, the description must carry the behavioral burden. It says only that the result is 'All tracks the user has Liked,' and does not disclose pagination, result limits, read-only behavior, or anything about how the tracks are returned.

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 highly concise, front-loads the core scope, and contains no filler words. Every word contributes to the meaning.

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 zero-parameter tool, the description provides enough to understand the basic operation, but without annotations or an output schema it does not disclose pagination or response shape. The agent can still invoke the tool correctly with no arguments, but may be surprised by the result format.

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?

There are zero parameters and the input schema covers the parameter space completely, so a parameter explanation is unnecessary. The no-parameter baseline of 4 applies.

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 identifies the resource ('tracks') and the scope ('user's Liked'), so an agent can tell this returns liked/saved tracks. It lacks an explicit verb like 'get' or 'list', and it does not explicitly differentiate itself from sibling tools such as get_top_tracks or get_recently_played.

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 wording implies it should be used when the agent needs the user's liked tracks, but there is no explicit when-to-use guidance or mention of alternatives. It neither states exclusions nor provides conditions for choosing a sibling tool.

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