Delete Video

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

Annotations declare destructiveHint=true and idempotentHint=true, but the description adds what those hints cannot: the exact deletion criteria and that they are configurable in the toolkit's config file, the dry-run behavior ('without confirm, nothing is deleted and the error describes the video'), and the 52-unit quota cost. This is substantive behavioral context beyond structured fields.

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?

Four compact paragraphs, each front-loaded with its most important fact: action, eligibility, safety gate, cost. No sentence is filler and the destructive nature is stated in the first line.

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?

With an output schema present, return values needn't be described. The description covers permanence, eligibility, the confirm precondition, the fallback path, and quota cost — everything needed to invoke this destructive 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?

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining the consequence of omitting confirm, which turns a simple field into a safety gate. It doesn't elaborate on the video ID/URL formats or channel selection, but those are already fully documented 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?

States a specific verb and resource ('Permanently delete one of your videos') and immediately bounds the scope of what can be deleted here versus elsewhere. An agent can distinguish it from sibling delete tools (delete_comment, delete_playlist, delete_caption) without opening any schema.

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?

Gives explicit eligibility criteria (max ~100 views; public videos within 7 days), names the alternative for everything else ('must be deleted in YouTube Studio'), and states the confirm precondition. No inference is required to decide whether this tool applies.

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