get_user_top_tracks

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the period options and default user behavior ('Defaults to the authenticated account'), which is useful. However, it does not disclose pagination behavior, rate limits, or what happens when the user is not found. With annotations covering the core safety traits, a 3 is appropriate.

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 compact and front-loaded with the core purpose in the first sentence. The parameter list is terse and scannable. It earns a 4 because it is efficient, though the parameter explanations are slightly repetitive of the schema names.

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?

The tool has an output schema, so return values are covered elsewhere. The description covers the main parameters and the default user behavior. However, it does not mention pagination behavior, error cases, or how 'overall' period differs from the others. For a read-only list tool with an output schema, this is adequate but not complete.

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 0%, so the description must compensate. It does explain all four parameters: user, period, limit, page. However, the explanations are minimal—'Results per page' and 'Which page of results to fetch' add little beyond the schema's names and defaults. The period values are enumerated, which is helpful, but the description does not clarify the meaning of 'overall' or the exact format of the user parameter. Baseline 3 is fair.

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 states a specific verb and resource: 'Get a user's most played tracks over a period.' This clearly distinguishes it from siblings like get_user_recent_tracks (recent, not top) and get_user_top_artists (artists, not tracks). It could be slightly stronger by explicitly naming a sibling, but the core purpose is unambiguous.

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 implies usage context: it is for reading a user's top tracks over a period, with period options listed. However, it does not explicitly state when to use this tool versus alternatives like get_user_recent_tracks or get_user_top_albums. The 'period' parameter explanation gives some context, but no direct when/when-not guidance is provided.

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