delete_video

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

Description explicitly says 'Permanently delete' and 'Irreversible', which covers the critical behavioral trait for a destructive operation. No annotations provided, so description carries full burden; this disclosure is sufficient but could mention side effects (e.g., removal from playlists) or auth requirements.

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?

Extremely concise at two sentences, front-loading the core action and consequence. Could benefit from a brief note on parameters or use cases without becoming verbose.

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 simple destructive tool with two parameters and no output schema, the description is incomplete. It lacks guidance on parameter usage, prerequisites, and how this tool fits with siblings (e.g., dry_run testing or verifying video ID).

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?

Zero schema description coverage; description adds no value for parameters (video_id and dry_run). dry_run's purpose (preview without deletion) is not explained, leaving ambiguity. Parameter names are somewhat self-explanatory but not explicitly detailed.

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?

Clearly states the tool deletes a video permanently. Distinguishes from sibling tools (e.g., update_video, upload_video) by specifying deletion action and 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?

No guidance on when to use this tool over alternatives (e.g., update_video or delete_playlist). Does not mention the dry_run parameter for safe testing or prerequisites like ownership.

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