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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true). The description adds two genuinely useful facts beyond them: `likeCount` is the release's fan count and the call costs 1 credit. It does not explain pagination behavior despite a cursor param, so it earns partial credit only.

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?

Three short, front-loaded sentences with minimal waste and the core purpose up first. Slightly terse in that `likeCount` is the only return field called out, but nothing is padded.

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 no output schema, the definition covers purpose, one return field, and cost, but omits pagination semantics and the meaning of `limit`/`cache_max_age`. It is adequate but not complete for a 4-param paged endpoint.

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 50%: `id` and `cursor` are documented in the schema, but `limit` (default 25) and `cache_max_age` are described nowhere. The description adds no parameter meaning to compensate for the gap, leaving two params opaque.

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 resource: an artist's albums, singles and EPs on Deezer, tied to a Deezer artist id. It is clearly distinct from deezer_artist (artist info) and deezer_artistTopTracks (top tracks) by naming the collection it returns, though it never explicitly says 'list all releases for an artist' or names those siblings.

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 explicit when-to-use statement and no alternatives are named. The scope detail ('albums, singles and EPs') implies coverage, but an agent gets no guidance on choosing this vs deezer_artist, deezer_artistTopTracks, or deezer_album.

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