Get Spotify Podcast Show Episodes

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds the useful behavioral detail that it returns 'one bounded page', indicating the paginated nature of results. This goes beyond the annotations and helps the agent understand that repeated calls with offset may be needed for full results.

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 a single sentence that is concise and front-loaded. It states the core action, the resource, and a key constraint ('bounded page') without any fluff, earning its place fully.

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 that the tool is a simple read-only paginated listing, the combination of a rich input schema (with defaults and ranges), strong annotations (read-only, idempotent, non-destructive), and an output schema means the description does not need to explain everything. It covers the essential contextual detail of pagination and exact ID requirement. However, it lacks any mention of when to use this vs. alternative show-related tools, so it is not fully complete.

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?

The description has 0% schema coverage: it does not mention limit or offset semantics. It only refers to 'exact Spotify show ID', which maps to show_id but adds no new meaning. The phrase 'one bounded page' hints at pagination but does not explain how limit/offset work, leaving the agent to rely solely on the schema defaults and titles.

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 uses a specific verb ('Return') and resource ('episodes for an exact Spotify show ID'), clearly conveying what the tool does. It also distinguishes from siblings like spotify_podcast_show (likely show details) and spotify_podcast_episode (single episode) by explicitly focusing on the episodes list for a show.

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 usage through 'for an exact Spotify show ID', indicating that this is for listing episodes when you already have the show ID. However, it does not explicitly mention when to use this tool versus alternatives like spotify_podcast_show or spotify_search, nor does it provide exclusions or alternative tool names.

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