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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the description's real contribution is cost disclosure: completed lookups consume credits and repeated requests may purchase the same data again, which materially affects agent behavior. The figures are internally inconsistent ('at least 10 Nexscope credits' versus '1 credit per request'), which weakens otherwise useful pricing context.

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 is correctly front-loaded, but the remainder is pasted pricing boilerplate ('Spotify Search API View Pricing Search Spotify 1 credit per request ... Examples are not guaranteed prices') that repeats the credit point three times and contradicts itself. Roughly half the text is redundant or non-actionable.

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 description does list the entity types returned, which is the key missing piece, and it covers cost. But it leaves result volume/pagination unexplained and introduces a nonexistent parameter, so an agent still has gaps before calling it confidently.

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% for the single 'query' parameter, so the baseline is 3. The description adds no meaning about query syntax, matching behavior, or result limits, and instead mentions a 'type=podcasts' argument that the schema does not expose, which risks an invalid call rather than clarifying the one real parameter.

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 first sentence gives a specific verb and resource and enumerates the entity types returned (tracks, artists, albums, episodes, podcasts, audiobooks), which distinguishes it from single-entity siblings like social_spotify_track or social_spotify_artist. It does not name those siblings explicitly, so an agent must still infer when to search versus fetch directly.

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 offers exactly one routing hint: use type=podcasts when podcast ids are needed for the podcast endpoints, which implicitly points at social_spotify_podcast. However, that hint references a 'type' parameter that does not exist in the schema, so the guidance is not actionable as written, and there is no advice on when to search versus call a direct lookup tool.

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