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

Annotations already declare readOnly and open-world behavior, but the description adds real context beyond them: the credit cost per call, and the fact that postCount is always null because Deezer exposes no episode count — a concrete trap an agent would otherwise misread as missing data. It does not cover error cases (invalid id, out-of-credits) or auth needs.

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?

Four short sentences with the payload summary front-loaded and the null caveat plus cost at the end. Sentence one duplicates the title, which is minor waste, but nothing else 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?

With no output schema, the field enumeration plus the postCount explanation carries the return-shape burden adequately, and the credit cost is stated. What remains thin is the missing link to deezer_podcastEpisodes and any explanation of cache_max_age, which leaves real gaps for a two-parameter tool.

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 only 50%: `id` is documented in the schema as a numeric Deezer podcast id, but `cache_max_age` has no description anywhere. The description mentions no parameters at all, so it does nothing to compensate for the undocumented cache control.

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?

"Podcast details" names the resource and adds the concrete payload fields (title, description, artwork, fans), so an agent knows what it gets back. It never distinguishes itself from the adjacent deezer_podcastEpisodes or spotify_podcast, so the sibling boundary is left implicit.

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 statement of when to use this versus deezer_podcastEpisodes (episode listing) or deezer_search (discovery), and no guidance on where a valid podcast id comes from. Usage is only inferable from the tool name.

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