Get Saved Spotify Episodes

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

Annotations already declare this as safe/read-only/idempotent. The description adds the behavioral detail of returning a single bounded page, which clarifies pagination behavior. It also scopes to the current user's library, providing context beyond annotations.

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?

Single sentence, 11 words, front-loaded with the core purpose. No redundant or extracted 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?

For a simple read-only list tool with rich annotations and an output schema, the description adequately covers the key behavior. It does not need to explain return values (output schema exists) and the scope is clear.

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 0% and the description does not directly mention limit/offset. However, 'bounded page' implies pagination, and the schema provides clear names, defaults, and constraints for the two parameters, offering minimal but adequate compensation.

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 action 'Return' and the resource 'episodes saved in the current user's library,' and specifies 'one bounded page' indicating pagination. This distinguishes it from siblings like spotify_saved_tracks or spotify_saved_albums by resource type.

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 context (fetch saved episodes) but does not explicitly name alternatives or exclusions. The title and description make it clear when to use this tool versus similar sibling tools for tracks or albums, but explicit when-not guidance is absent.

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