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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-catalog profile is covered. The description adds that results contain artist profiles and IDs, which is useful return context, but says nothing about pagination behavior, result caps, or rate limiting.

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 with no filler; the purpose statement is front-loaded and the follow-on usage hint is secondary. Appropriately sized for the tool's role.

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?

An output schema exists, so return-value explanation is not required, and 100% schema coverage handles parameters. Combined with annotations covering the read-only/open-world profile, the description leaves little an agent needs missing, though a sibling reference would round it out.

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 all 11 parameters (limit, offset, isPrefix, includeAuthors, etc.) are already documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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+resource ('Search Spotify for artists by name or keyword'), and the scope ('for artists') distinguishes it from the many parallel search tools like spotify_tracks_search or spotify_albums_search. It stops short of explicitly naming the generic spotify_search sibling, so an agent infers rather than reads the distinction.

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 second sentence hints at follow-on usage ('use a returned artist ID to fetch that artist's albums, related artists, or profile'), which implies this is an entry-point/lookup tool. However, there is no explicit when-to-use vs alternative guidance, e.g. no contrast with spotify_search or the other typed search endpoints.

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