Delete a video from the connected YouTube channel

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

Annotations already flag destructiveHint:true, but the description goes far beyond by detailing the irreversibility (no trash, no undelete, loss of views/comments/links) and the rationale behind confirmTitle to prevent deleting the wrong video. It also notes the 0-credit cost and channel prerequisite. This adds substantial behavioral context beyond the annotation.

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 long (~150 words) but every sentence is purposeful: it front-loads the action, then explains irreversibility, the confirmation protocol, the alternative, and prerequisites. The structure is logical and well-paced, though slightly verbose; it could be tightened without losing information.

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 tool with a multi-step confirmation flow, conditional parameters, and an alternative usage path, the description covers all necessary context: how to call, what to expect, when to use an alternative, and prerequisites. Even without an output schema, an agent has everything needed to invoke this 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 schema covers all three parameters with descriptions (100% coverage). The description adds meaning by explaining the confirmTitle requirement's conditionality (public or any views/comments) and tying videoId to list_youtube_videos. It reinforces the workflow context, slightly elevating value beyond the schema baseline.

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 opens with 'PERMANENTLY delete a video from the connected YouTube channel', which is a specific verb+resource statement that unambiguously defines the operation. It explicitly distinguishes itself from the reversible update_youtube_video tool and other sibling delete tools by emphasizing its irreversible nature.

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 provides a detailed two-step confirmation workflow (call without confirm first, get user confirmation, then call with confirm:true and confirmTitle). It explicitly routes users to update_youtube_video for reversible privacy changes, and points to list_youtube_videos as the source for videoId. This is comprehensive and leaves no ambiguity about when to use this tool vs alternatives.

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