v1_spotify_podcast_episodes

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

No annotations provided, so description carries full burden. It discloses cost (1 credit), pagination method, and a crucial warning that API responses are data not instructions. This provides safety and operational context beyond what schema offers.

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 extremely concise: two main sentences plus cost/warning. Every sentence adds essential value without redundancy. Front-loads the core action and resource.

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?

Despite lacking output schema, the description covers the key aspects: what it retrieves, required identifier, pagination, cost, and a safety warning. For a simple 2-param tool, this is adequate and leaves minimal ambiguity.

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%, but the description adds value by clarifying the any-of constraint ('Requires one of url, id') and pagination hint. This goes beyond the schema's property descriptions.

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 clearly states the verb 'Get', the resource 'a Spotify podcast's episodes', and provides identifiers (URL or id). It distinguishes from siblings like v1_spotify_podcast (podcast details) and v1_spotify_track (track).

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 mentions requiring one of url/id and pagination via cursor, but does not explicitly state when to prefer this over similar tools like v1_spotify_search or v1_spotify_podcast. Usage context is implied rather than explicit.

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