saved_tracks

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 behavioral disclosure, and it discloses nothing. It does not state ordering, pagination across the liked-songs collection, authentication requirements, or what a response contains, leaving the agent blind on a retrieval operation over a potentially large 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?

It is very short, but this is under-specification rather than conciseness - a four-word fragment that earns no information. There is no front-loaded statement of what the tool does, so brevity here provides no benefit to the agent.

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, an undocumented parameter, and no usage guidance, the definition is completely inadequate for a retrieval tool inside a large, cluttered sibling set. An agent cannot reliably distinguish it from saved_albums or decide how to call it.

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 single parameter (limit) has 0% schema description coverage, and the description adds no meaning whatsoever about it. Nothing explains whether limit caps returned tracks, defaults, or its maximum, so the schema gap is entirely uncompensated.

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 phrase 'Your Liked Songs.' restates the tool name (saved_tracks) as a noun fragment without a verb, so it never says what operation is performed (list? fetch? save?). It implies retrieval of the user's liked tracks, but it is essentially a tautological label rather than a statement of purpose.

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?

There is no when-to-use guidance at all: no mention of when this differs from sibling tools such as saved_albums, top_tracks, recent_tracks, or save_tracks, and no prerequisites or exclusions. The agent must infer everything from the tool name alone.

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