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

Annotations already declare this is a read-only, open-world lookup, so the bar is lower. The description usefully adds result ordering ('most popular first') and a credit cost/rate-limit style signal, but says nothing about pagination behavior even though a cursor parameter exists.

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 short sentences, front-loaded with purpose, followed by ordering semantics and cost. Every sentence carries information an agent cannot get from the structured fields alone.

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 lookup with no output schema, the description covers purpose, ordering, and cost but omits pagination and limit semantics on a 4-parameter tool with half of the parameters undocumented. It is adequate to start calling the tool, but not sufficient to invoke it correctly with limit/cursor on repeat calls.

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?

With only 50% schema description coverage, the description must compensate for the gap. It adds nothing about id format beyond the schema, nothing about what limit bounds/means (default 25, max?), nothing about cursor semantics, and nothing about cache_max_age — all left entirely to 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?

States a specific verb+resource ('Artist top tracks') and clarifies it means an artist's most popular tracks on Deezer, so an agent can tell it apart from deezer_artist or deezer_artistAlbums. It stops short of explicitly naming those siblings or stating what it excludes.

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?

Usage is only implied by the resource name: call it when you need an artist's ranked popular tracks and you already have an artist id. The 'Costs 1 credit' note gives cost context, but there is no explicit when-to-use/when-not guidance or mention of alternatives like deezer_track or deezer_search.

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