youtube_delete_video

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

The description discloses that the action is irreversible, which is a critical behavioral trait for a delete operation. However, it does not mention authentication requirements, potential errors, side effects on related data, or what happens on success. With no annotations, the description carries the burden, and this only partially covers it.

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 extremely concise, with two sentences and an argument listing, and all content is useful. It avoids redundancy and front-loads the key information, making every word earn its place.

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 delete tool with one parameter and no annotations, the description covers the action and irreversibility but omits return value and authentication context. The lack of an output schema makes the missing return value information a noticeable gap, though the tool's simplicity partially mitigates this.

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 description repeats the parameter name from the schema and adds 'YouTube video ID to delete,' providing minimal additional context beyond the schema's 'Video Id' title. No format or source guidance is given, so the description does not fully compensate for the 0% schema description coverage.

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 clearly states 'Delete a video' with a specific verb and resource, and it is distinct from sibling tools like youtube_update_video or youtube_upload_video. The action is unambiguous and directly conveys the tool's purpose.

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 explicit guidance on when to use this tool versus alternatives, nor any prerequisites or warnings about ownership. Usage is implied by the name and description, but no exclusions or alternative recommendations are provided.

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