remove_saved_shows

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

With no annotations to lean on, the description carries the safety burden well: it discloses the mutation, the DELETE semantics, and the critical plan-by-default, commit-only-with-dry_run=false behavior. It does not mention reversibility or authorization, but the dry-run safety mechanism is the most important behavioral detail and it is present.

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 compact yet information-dense: endpoint, scope, alternatives, and commit semantics all appear in two sentences without repetition. Every clause adds useful guidance for an agent deciding to call this tool.

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 destructive bulk operation with no annotations and no output schema, this description covers the essential call decisions: what it removes, how it differs from siblings, and how to preview before committing. It could say a bit more about the shape of the plan/result, but it is complete enough for correct invocation.

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 the schema already documents all three parameters. The description adds beyond that by explaining the planning behavior tied to dry_run and the cross-checking of saved IDs, which gives the parameter meaningful operational context.

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 a specific action — bulk-removing shows from the library — and anchors it to a concrete API endpoint (DELETE /me/shows). It explicitly distinguishes this tool from siblings by noting unsubscribe_from_show for single shows and remove_saved_episode for 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?

It gives direct routing guidance by naming the removal verb family and the exact sibling alternatives for single-show and episode removals. It also explains the preview-vs-commit flow, telling the agent to pass dry_run=false when actually committing.

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