remove_dead_videos

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

With no annotations, the description carries the full transparency burden. It discloses the critical safety behavior: 'By default runs in dry_run mode — set dry_run=False to actually remove.' This clearly distinguishes preview from execution. However, it does not elaborate on side effects of actual removal or the role of db_path.

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 appropriately sized, front-loaded with the action statement, and each sentence earns its place. It efficiently explains the purpose, the dry_run behavior, and parameter details without extraneous content.

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?

The tool has an output schema (not shown), so return values need no explanation. The description covers the core purpose and dry_run, but omits any explanation of db_path, which is a parameter with a default. This leaves the description incomplete for a fully self-sufficient tool.

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 description adds meaning for the dry_run parameter, explaining it as 'If True (default), only preview; set False to execute.' However, db_path is completely unexplained, and schema description coverage is 0%. The description partially compensates but leaves a significant gap.

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 purpose with a specific verb and resource: 'Remove all dead/private/blocked videos from their playlists.' It distinguishes from sibling tools like find_dead_videos, as this tool performs removal rather than identification.

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 explaining the dry_run default and how to execute, but it does not explicitly contrast with alternatives like find_dead_videos or state when this tool should be used over others. The guidance is implied rather than explicit.

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