Delete Video

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds substantial context they cannot convey: the permanence of the deletion, the hard view/age eligibility limits, the confirm-gate failure mode, and the 52-unit quota cost. This is rich behavioral disclosure 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 short sentences, front-loaded with the action and its permanence, then eligibility limits, then the confirm gate, then quota. No filler and no repetition of the title or schema.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. Combined with the eligibility limits, confirmation gate, and quota disclosure, an agent has everything needed to invoke this destructive tool responsibly.

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 description coverage is 100%, so the baseline is 3 and the schema already documents 'video', 'confirm', and 'my_channel'. The description nonetheless adds the behavioral consequence of omitting confirm ('nothing is deleted and the error describes the video'), which clarifies the two-phase confirmation semantics beyond the raw schema text.

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 first sentence states a specific verb and resource ('Permanently delete one of your videos') plus the crucial qualifier that the deletion is permanent. It is unambiguous against siblings like update_video, remove_from_playlist, or delete_comment, which operate on different resources.

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?

Explicitly states the conditions under which this tool works (recent, ≤100 views, uploaded within 7 days if public) and names the fallback for everything else ('Anything else must be deleted in YouTube Studio'). This is exactly the when/when-not/alternative structure an agent needs.

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