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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description adds genuinely non-structured behavior: results are sorted by name and paginated at 50 per page by default. It stops short of describing what an empty search returns or how the picture field is delivered.

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?

Front-loaded with the resource and payload, and the paging behavior arrives in the same compact sentence. The middle clause 'Songs belong to an artist; create the artist first' reads as a misplaced note about the create/attach workflow rather than this listing tool, costing a little focus.

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, the description correctly carries the return-value burden by naming the counts and picture per artist, and it covers sorting and default paging. Only the shape of the response envelope and total-count/pagination metadata are left unstated.

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 coverage is 100%, so q/limit/offset are already documented in the schema, and the description largely restates them ('pass q to search by name, and limit/offset to page'). It confirms the search-vs-paging split but adds no format, matching, or boundary detail beyond the schema.

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 (artists) and what a returned record contains (name, song count, photo count, picture), which distinguishes it from single-item siblings like get_artist and from list_songs/list_videos. It opens with a noun phrase rather than an explicit verb, but the intent to enumerate a collection is unmistakable.

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?

It offers 'create the artist first', which is a related-workflow hint rather than guidance on choosing this tool over get_artist or list_artist_photos. There is no statement of when the collection view is preferred over a single-artist fetch, so usage is only implied.

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