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

Annotations already declare readOnlyHint, openWorldHint, and non-destructive. The description adds genuinely new behavioral context beyond that - cost of at least 10 Nexscope credits, that cost depends on requested options, and that repeated requests may purchase data again. However the cost figures are muddled by a competing '1 credit per request' line, weakening the transparency.

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?

The purpose sentence is well front-loaded, but the remainder is verbose pricing boilerplate ('View Pricing Get Spotify podcast 1 credit per request', 'Examples are not guaranteed prices') that is repetitive and partially self-contradictory. Several sentences do not earn their place.

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-lookup with annotations covering safety and a fully documented 2-param schema, the description covers how to address the resource and the cost model. But it omits any hint of what the lookup returns and the conflicting credit figures could mislead an agent about cost.

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 100%, so baseline is 3, but the description earns extra by explaining the domain quirk that Spotify internally names podcasts 'shows' and that podcast URLs therefore use the /show/ path - meaning an agent can recognize a valid URL that the schema alone wouldn't flag. That is real meaning added beyond 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 and resource: 'Retrieves detailed information about a Spotify podcast by its id or URL,' and adds a clarifying note that Spotify calls podcasts 'shows' internally with /show/ URLs. It does not explicitly differentiate itself from siblings like social_spotify_podcast_episodes or social_spotify_search, but the purpose is unambiguous.

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 implies the caller supplies an id or URL but gives no guidance on when to use this tool versus the closely related social_spotify_podcast_episodes or social_spotify_search. No exclusions, no preconditions, no alternative routing.

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