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 discloses the 500-item cap and that fetch_all overrides limit/offset, which is useful behavioral context. However, it does not mention auth requirements, rate limits, or the return structure, which could be relevant for an agent.

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?

Two sentences with zero waste. The purpose is front-loaded, and the key behavioral nuance (fetch_all cap) is included without padding. Every word earns its place.

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 the tool's simplicity and full schema documentation, the description adequately covers the essential behaviors: pagination via limit/offset, the fetch_all mode, and the 500-item cap. No output schema exists, so return format is not specified, but for a list retrieval this is a minor gap.

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%, so all parameters are documented. The description repeats the fetch_all behavior and the 500 cap, which are already in the schema. Since the schema does the heavy lifting, the description adds minimal extra value beyond what an agent would read from the schema.

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 tool retrieves podcast episodes saved in the user's library, using a specific verb and resource. This distinguishes it from sibling tools like get_saved_tracks or get_saved_shows, even without naming them. The mention of fetch_all behavior adds clarity about its scope.

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 provides clear context on how to use the tool, including the distinction between fetching a single page and using fetch_all for the full collection. It does not explicitly name alternatives or exclusions, but the resource specificity (podcast episodes) makes selection straightforward among the many get_saved_* siblings.

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