spotify_save_episodes

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

With no annotations, the description carries the full burden. It discloses a key behavioral constraint (max 50 per call) but omits details like idempotency, authentication requirements, or effects of duplicate saves. Some information is provided, but more context would improve safety.

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 two sentences and tightly focuses on the essential action and constraint. No extraneous information, and the key verb is front-loaded.

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 save operation with one parameter, the description adequately covers the main action and a practical limit. It could mention error handling or idempotency, but given the low complexity and existence of an output schema, it is reasonably complete.

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 compensate. It adds the max 50 constraint but does not explain the format or source of episode IDs. The schema already shows it's an array of strings, so the description adds marginal value beyond that.

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 ('Save podcast episodes to your library') and includes a specific constraint ('max 50 per call'). It distinguishes from siblings like save_tracks and save_albums by specifying the 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 by stating what the tool does, but does not explicitly provide guidance on when to use it versus alternatives (e.g., adding to playlists or checking saved episodes). Context from sibling naming partially compensates.

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