remove_saved_episode

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

With no annotations provided, the description carries the full behavioral burden. It adds meaningful behavior beyond the schema by disclosing the dry-run PLAN default, the explicit commit mechanism, and the pre-check against saved episodes. It does not detail irreversibility or API side effects, but the safety-first default is a strong disclosure.

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 dense sentences convey purpose, endpoints, sibling alternatives, default behavior, and how to commit. The phrase 'removal verb:' is slightly awkward, but the description is otherwise tightly packed with no filler and leads with the core action.

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 removal tool with no output schema and no annotations, the description covers the essential call semantics: what is removed, how the safety default works, and how to actually perform the removal. It does not describe error conditions or PLAN details, but the core decision-making and invocation knowledge is present.

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 description coverage is 100%, so the schema already explains dry_run, episode_ids, and response_format. The description adds context about cross-checking and PLAN behavior but does not add parameter-level meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

States the specific verb 'Remove episodes from your library' and the underlying API endpoint (DELETE /me/episodes). It also names sibling tools with the same removal intent (remove_saved_shows, delete_playlist_snapshot) and scopes the difference by resource type, so the agent can distinguish it from nearby tools.

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?

Provides clear operational guidance: it cross-checks saved status, previews a PLAN by default, and requires dry_run=false to commit. It names related removal siblings but stops short of explicit when-to-use versus alternatives like remove_saved_items or remove_from_library, leaving some routing to inference.

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