clean-playlist

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

With no annotations, the description carries the full burden of disclosing behavior. It states the dry-run default, that passing dryRun: false deletes, and provides quota cost context (1 unit/page, 50 units per item). It also explicitly mentions the types of items removed, making the destructive nature clear.

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 concise two-sentence structure that front-loads the core action and scope, then provides crucial behavioral defaults. No filler or redundancy.

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 5-parameter tool with no output schema, the description covers the workflow, dry-run default, deletion thresholds, and quota implications. It does not detail the plan's return structure, but the provided context is sufficient for an agent to select and invoke the tool correctly.

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 input schema already documents all 5 parameters with 100% coverage. The description adds value by mapping the removal categories to parameters (tombstones, duplicates, channel videos), clarifying the dryRun effect, and providing quota details not present in 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's function with specific verbs ('Scan', 'plan removal') and resources ('playlist', 'tombstones', 'duplicates', 'videos from given channels'). It distinguishes itself from CRUD siblings by focusing on bulk playlist cleanup with a dry-run workflow.

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 the appropriate use case by describing the scanning and removal capabilities, and explains the dry-run vs. actual deletion behavior. It does not explicitly cite alternatives like remove-from-playlist or list exclusions, but the context is clear enough for an agent to know when to invoke this tool.

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