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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the flat 2-credit cost, that empty results and failures are never charged, that cache=true gives a free 24h cache hit while the default is always fresh, and that cursor pagination is used. These are non-obvious, decision-relevant behaviors an agent would not otherwise know.

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 description is short and front-loaded with the purpose and key fields, followed by cost, caching, and failure behavior. There is minor redundancy in saying 'flat 2 credits' and then 'Costs 2 credits' within consecutive clauses, but overall every sentence earns its 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?

Given there is no output schema, the description usefully names the returned episode fields and indicates cursor pagination, while the schema covers URL formats and parameter defaults. It could have described response envelopedetails or episode ordering, but an agent has enough to select and invoke the tool correctly.

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%, so the parameters are already well documented. The description reinforces cursor pagination, flat pricing, and cache behavior, but it does not add substantial meaning beyond what the schema already provides for each 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 description identifies the tool as a podcast episode archive and lists key returned fields (previewUrl, releaseDate, explicit), which makes its purpose clear and distinguishes it from sibling tools like spotify_podcast. It lacks an explicit imperative verb like 'fetch' or 'list,' but the resource and field list leave little ambiguity.

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 provides useful operational context such as cost, caching, and pagination, but it never explicitly states when to use this tool versus alternatives like spotify_podcast, spotify_album, or spotify_search. Usage is implied by the name and 'episode archive' phrasing rather than prescribed.

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