Delete a video

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

Annotations already flag destructiveHint and idempotentHint, but the description adds the critical behavioral facts: the deletion is permanent, irreversible, and gated on user confirmation. It does not spell out the two-call confirmation_token handshake itself, leaving that to the schema.

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?

Three short sentences, zero filler, with the destructive consequence and the confirmation requirement front-loaded before any call is attempted.

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 single-resource tool with annotations covering the safety profile and a schema covering the confirmation token flow, this is nearly complete. Minor residual gap: no mention of what happens to dependent resources (comments, playlists entries) or of quota cost.

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 67% and two of three parameters are described in the schema; only video_id is undocumented but is self-evident as the required identifier. The description adds no format, scoping, or channel-selection detail beyond 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 a video from YouTube'), which cleanly separates it from sibling deletions such as delete_playlist, delete_comment, and delete_captions.

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 a clear precondition — the user's confirmation is always required — which tells the agent this is not a fire-and-forget call. It does not name alternatives (e.g., set_visibility for unlisting rather than deleting), so no explicit when-not guidance.

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