get_user_top_tracks

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

The description clearly details the return structure including success/error handling, but does not mention authentication requirements or rate limits. However, since no annotations are provided, the description carries full burden and is largely transparent.

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 well-structured with clear sections for arguments and returns, but it is somewhat lengthy due to including the full return schema. However, this is justified as there is no output schema in the tool definition.

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 no annotations and no output schema, the description provides a comprehensive picture including return structure. Missing authentication context, but overall completeness is high for a data retrieval tool.

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 has 0% description coverage, but the tool description fully compensates by defining each parameter, defaults, options for time_range, and constraints on limit/offset. This adds significant meaning beyond the schema.

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 'Get user's top tracks from Spotify' with a specific verb and resource. It distinguishes from sibling tools like 'get_user_top_artists' (different resource) and 'get_artist_top_tracks' (different scope).

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 does not explicitly guide when to use this tool versus alternatives like 'get_artist_top_tracks' or 'get_user_top_artists'. Usage is implied by the purpose, but no exclusions or context for when-not-to-use are given.

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