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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing cost ('at least 10 Nexscope credits') and that 'Repeated requests may purchase data again' — non-obvious billing behavior an agent must know before paginating. But the pricing sentences are self-conflicting ('at least 10 credits' vs '1 credit per request'), which weakens the disclosure.

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 first three sentences are front-loaded and useful. The trailing block ('Completed lookups cost at least 10 Nexscope credits... Spotify Podcast Episodes API View Pricing... Examples are not guaranteed prices') is pasted marketing boilerplate that repeats the pricing point and contradicts itself, diluting the actionable content.

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 three optional parameters, no required fields and no output schema, the description leaves the caller to infer that at least one of id or url must actually be supplied, and says nothing about what an episode record contains. The cost and pagination notes are the right additions but the input precondition gap remains.

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%, and every parameter (id, url, cursor) is already documented there with the id-vs-url alternative spelled out. The description's cursor sentence merely restates the schema. Baseline 3 applies.

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: 'Returns episodes for a Spotify podcast.' An agent can tell it retrieves an episode list rather than podcast metadata or search results. It does not, however, name or contrast itself with the sibling social_spotify_podcast, which likely returns the podcast itself.

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 only usage instruction is pagination: 'Pass the cursor returned by a response to get the next page.' There is no guidance on when to call this instead of social_spotify_podcast or social_spotify_search, and no stated precondition (such as needing a podcast id from a prior lookup).

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