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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful context about what each result contains, including covers, length, analysis status, and available lyric/Canvas/music-video offerings.

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 two sentences and front-loads the returned content before the usage cue. It is appropriately sized with no redundant or wasted phrasing.

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 read-only list tool with full parameter documentation and annotations, the description is mostly complete: it explains the result contents and the primary use case. It is only missing explicit sibling differentiation, especially against list_songs and get_song.

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 q, limit, offset, and artist_id are already documented in the schema. The description does not add meaning beyond the schema for filtering, paging, or limiting.

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 states a specific verb and resource: it shows the person's songs as a list, and it names the returned contents such as covers, length, analysis status, and available video types. It is clear, but it does not explicitly distinguish itself from siblings like list_songs or get_song.

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 gives an explicit usage cue: use it when the user wants to see or pick a song. However, it does not say when not to use it or name alternatives such as list_songs or get_song for narrower lookup needs.

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