get_top_artists

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It mentions that results are the most-played artists, but gives no information about ordering, return shape, authentication expectations, defaults to interpreted time_range, pagination-like behavior, or side effects.

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 extremely succinct and front-loads the core resource. No words are wasted, though the minimalism edges toward under-specification rather than elegant brevity.

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 tool with no annotations, no output schema, and two parameters whose semantics are not described, the description is too thin. An agent can infer that it fetches top artists, but it is not told how the time range changes the data or how to choose parameters appropriately.

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%, and the description says nothing about the meaning or effect of 'limit' or 'time_range'. While the schema lists valid enums and defaults, the description does not help an agent understand what short_term versus long_term means or how limit affects the result.

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 'The user's most-played artists' clearly identifies the resource being retrieved, and the tool name supplies the get action. It distinguishes itself from sibling tools like get_top_tracks by naming artists specifically, but it is still a noun phrase rather than an explicit statement of what the tool does.

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 guidance about when to use this tool instead of alternatives such as get_top_tracks, get_recently_played, or get_saved_tracks. The description gives no context for choosing among the many sibling music-retrieval tools.

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