Artist overview

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds the shape of the returned data, which is genuinely useful given there is no output schema, but says nothing about latency, rate limits, or behavior when an artist is unknown.

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?

A single front-loaded sentence that leads with the resource and then lists contents without filler. The enumeration is dense but each item earns its place since no output schema exists, though a brief clause on the artist identifier forms would have made it complete.

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?

With no output schema and only two well-documented parameters, the description's field inventory is the main thing an agent needs to judge relevance, and it delivers that. Minor gaps remain: no statement of what is omitted when data is unavailable, and no indication that top_tracks caps the listed tracks.

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% – the artist parameter already documents accepted id/URI/URL forms and top_tracks documents its 1-10 bound. The description adds no meaning beyond that, so the baseline of 3 applies; it also never mentions that top_tracks shapes the 'top tracks' section it advertises.

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 names the resource precisely ('One artist's profile') and enumerates the payload surface (listeners, followers, rank, top cities, top tracks, latest release, discography counts, related artists, bio, links), so an agent knows exactly what it retrieves. It stops short of a 5 because it never distinguishes itself from close siblings like get_artist_insights or get_artists_stats, leaving ambiguity about which artist tool to pick.

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 when-to-use guidance, no exclusions, and no mention of alternatives such as get_artist_insights, get_related_artists, or get_artists_stats. The agent must infer the routing decision from the field list alone.

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