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

Beyond the annotations, the description discloses important consequences: shorts already made from the video stay, the long-video slot is freed, and the user cannot restore the deleted video from the app. It also tells the agent to confirm with the user first, which is critical behavioral guidance for a destructive operation.

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 four short sentences with no wasted text. The primary purpose is front-loaded, followed by side effects, required confirmation, and irreversibility.

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-parameter deletion tool, the description covers what is deleted, what remains, the slot side effect, required user confirmation, and irreversibility. Combined with the destructive annotation and complete schema, an agent has enough information to invoke it 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?

The schema has 100% description coverage for the single required video_id parameter, including that it comes from list_videos. The description does not add any further parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 gives a specific verb and resource: delete an imported long video. It also states the scope and consequence: freeing a long-video slot, while shorts made from it remain. This clearly distinguishes the action from related video and short-management tools.

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?

It provides clear usage context: use this to free a long-video slot, and confirm the video with the user first. It does not name an explicit alternative tool or explain when deletion should be avoided in favor of another action, but the confirmation prerequisite is strong guidance.

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