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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-catalog profile is covered. The description adds that results carry show profiles and IDs, but says nothing about pagination behaviour, result counts, or what a search with no query returns.

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 tight sentences, front-loaded with the action and followed by the useful chaining hint. Nothing is padded, though the second sentence could have been spent on sibling differentiation instead.

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?

An output schema exists so return values need no explanation, and the description does point at follow-on tools. However, the schema exposes includeAuthors, includeAudiobooks and artist/album flags that imply broader, multi-entity results than 'podcast shows' suggests, and the description never reconciles that mismatch.

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% with 11 documented parameters, so the schema carries parameter meaning fully. The description adds no parameter-level detail, which is acceptable at this coverage but yields only the baseline score.

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 and resource: search Spotify for podcast shows by name or keyword, and explains what results contain (show profiles and IDs). It does not, however, differentiate itself from the sibling spotify_podcasts_search, which reads as the same job, leaving the agent to guess which one to call.

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 downstream guidance — use a returned show ID to list episodes or fetch show details — which implies the follow-on tools. But it never says when to prefer this over spotify_podcasts_search, nor any exclusions or prerequisites, so selection between near-identical siblings is left to inference.

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