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

Annotations already declare readOnlyHint, openWorldHint and non-destructiveness, so the safety profile is covered. The description does add genuinely useful non-schema information — paid lookups cost at least 10 Nexscope credits and repeated requests may re-purchase data — but that pricing text is internally inconsistent ('at least 10 credits' versus '1 credit per request'), which weakens trust in the cost signal.

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 sentences restate the same thing (retrieve artist by handle, returning name/followers/genres/related artists), then tack on pricing boilerplate that reads like scraped supplier documentation ('Spotify Artist API View Pricing Get Spotify artist...'). The core intent is front-loaded but roughly half the text earns no place.

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 simple two-parameter read-only lookup with no output schema, listing the returned fields is a reasonable substitute for a return spec. But the nonexistent 'handle' input and the garbled cost text leave an agent with an inaccurate picture of both how to call it and what it will be charged.

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 the baseline is 3, but the description actively misdirects: it says the tool 'accepts a handle' when the schema only exposes 'id' and 'url' with no handle property, and it never mentions the id-vs-URL choice the schema flags. This risks an agent passing a nonexistent argument.

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 ('Retrieves detailed information about a Spotify artist') and lists the fields returned, which distinguishes it from sibling entity-lookup tools like social_spotify_album, social_spotify_track and social_spotify_playlist. However, it says lookup is 'by their handle', a concept that does not exist in this tool's inputs.

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 at all: nothing says whether this is the right call versus social_spotify_search (to find an artist first) or whether an id or URL is preferred. The only conditional language is about billing, which is not usage routing.

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