spotify_get_saved_episodes

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

No annotations are provided, so the description carries the full burden. It mentions a limit of 50 but does not disclose pagination behavior, authentication requirements, rate limits, or what happens if more than 50 episodes are saved. The agent cannot infer the completeness of 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, clear sentence with no redundant information. It is efficient and front-loads the core purpose.

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 low complexity (1 param, output schema exists), the description is almost adequate. However, it lacks details on pagination or ordering, which are important for retrieving a potentially large set of saved episodes. It is not fully complete for a robust agent interaction.

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 schema has 0% description coverage, so the description must add meaning. It adds 'up to 50' for the 'limit' parameter, which is helpful but does not specify the range or behavior beyond the default. The description adds some value but leaves gaps.

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 'Get your saved podcast episodes', specifying the verb and resource. It distinguishes from sibling tools like spotify_get_saved_tracks and spotify_get_saved_shows by specifying 'podcast episodes'.

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?

No explicit usage guidelines or alternatives are provided. While the purpose is clear, the description does not indicate when to use this tool versus other similar retrieval tools (e.g., spotify_get_saved_shows). It is left to the agent's inference.

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