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

Annotations already establish read-only and open-world behavior, while the description adds two meaningful traits beyond them: episodes are returned newest first and the call costs 1 credit. It still omits pagination behavior beyond the cursor field and does not describe rate or limit characteristics.

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 sentences, front-loaded with the resource and ordering. The opening 'Podcast episodes' slightly duplicates the title, but the description is otherwise tight and efficient.

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 simple read-only list endpoint, the description gives the core context: which podcast, ordering, and credit cost. However, with no output schema and missing documentation for limit and cache_max_age, an agent lacks enough detail about page size and caching behavior.

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?

The description adds almost no parameter meaning beyond what is already in the schema: the required id is described there as a numeric Deezer podcast id, and cursor is schema-documented. The limit and cache_max_age parameters remain unexplained in both schema and description, and the description does not compensate for the 50% coverage gap.

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 the specific resource ('A Deezer podcast's episodes') and result ordering ('newest first'), so an agent can tell this lists episodes for a given podcast id. It does not explicitly differentiate from the nearby deezer_podcast metadata tool, which keeps it below a 5.

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 description says what the tool returns but gives no guidance on when to use it instead of alternatives such as deezer_podcast or deezer_search. 'Costs 1 credit' is useful context, but it is not routing guidance.

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