Get Show Episodes

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds real value beyond them by noting that each episode carries the user's resume point and that results are paginated, but it says nothing about rate limits, auth scope, or behavior for an unknown/invalid show id.

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 core purpose is front-loaded in one sentence, followed by a clean Args/Returns breakdown with no filler. The Returns line is somewhat redundant given a real output schema exists, but overall it is tight and scannable.

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?

For a three-parameter read tool with an output schema and full annotation coverage, the definition supplies enough to call it correctly: id format, pagination range, and the notable resume-point payload. Minor gaps remain around invalid-id behavior and any market/locale constraints.

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?

With 0% schema description coverage the schema gives only bare names and defaults, so the description must compensate — and it largely does, stating show_id accepts an ID, URI or open.spotify.com URL and bounding limit to 1-50. Offset is explained as a page skip, which is adequate but minimal.

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 names a specific verb and resource ("Get a podcast show's episodes") and adds a distinguishing detail: the user's resume point is included per episode. It separates itself from get_saved_episodes and get_saved_shows by scoping to a single show, though it never names those siblings explicitly.

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?

Usage is only implied — an agent can infer this tool is for browsing episodes of one known show, but the description never states when to prefer it over get_saved_episodes or get_saved_shows, nor does it mention prerequisites such as needing a valid show id from a show search/list.

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