getTopTracks

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

With no annotations, the description carries the full burden and discloses almost nothing behavioral: no mention of required user authorization, pagination, or return shape. Only the implicit 'Get' read operation and 'most-played' semantics are conveyed.

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?

Two tight sentences, purpose front-loaded, no filler. Every clause contributes to identifying the tool.

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-required-param read tool with fully documented schema, the description is adequate on purpose but silent on auth requirements and output characteristics. With no annotations and no output schema, a bit more behavioral context would help.

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%, so both parameters (limit, timeRange) are already fully documented with ranges and enum meanings. The description adds no parameter detail beyond the schema, which is the expected baseline.

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?

States a specific verb and resource ('Get the current user's top (most-played) tracks') with a clear scope modifier (time range). It is distinct from siblings like getRecentlyPlayed and getUsersSavedTracks, but never names a sibling to differentiate explicitly.

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 framing as 'the closest thing Spotify exposes to listening statistics' hints at intent, but there is no when-to-use guidance, no exclusions, and no alternatives named among the many siblings (getTopArtists, getRecentlyPlayed, getUsersSavedTracks).

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