getTopTracks

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

With no annotations provided, the description carries the full burden. It implies a read-only operation via 'Get' and adds context about listening statistics, but it does not disclose potential behavioral traits such as auth requirements, default time range (though in schema), or response format. This is a moderate disclosure for a simple read tool.

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 two sentences, front-loaded with the action and resource, and contains zero filler. Every clause serves a purpose, making it highly efficient.

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?

Given the tool's low complexity (2 optional params, no output schema), the description is mostly complete: it identifies the resource, scope, and purpose. It lacks an explicit statement about return format, but the phrase 'top tracks' implies a list. This is solid but not fully exhaustive.

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 100%, and both parameters (limit, timeRange) are well-documented in the schema. The description adds minimal extra meaning beyond the schema, only referencing 'over a given time range' which aligns with timeRange. Baseline 3 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 uses a specific verb+resource combination: 'Get the current user's top (most-played) tracks' and adds time-range scope. It clearly distinguishes from siblings like getTopArtists (tracks vs artists) and getRecentlyPlayed (top vs recent) by focusing on 'top' tracks and 'listening statistics'.

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 usage context by stating 'This is the closest thing Spotify exposes to listening statistics,' implying it's for statistical/analytical use cases. However, it does not explicitly mention when not to use it or name alternative tools, so it lacks the full guidance of a 5.

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