Venice Video Complete (cleanup)

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

No annotations are provided, so the description carries the full burden. It explicitly discloses the destructive behavior ('deletes server-side media') twice, which is a key behavioral trait. It also mentions auth methods (x402 wallet, API key). However, it doesn't disclose what happens to the queue record, whether deletion is reversible, or error behavior if called before download completes.

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 short but contains redundancy: 'deletes server-side media' appears twice ('deletes server-side media' and 'removes server-side media'), and the cleanup-hook concept is repeated. The auth info is useful but the duplication of the destructive behavior wastes a sentence in an already short description.

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?

With no annotations, no output schema, 0% parameter coverage, and a destructive side effect, the description should disclose more about preconditions (e.g., video must be in completed state) and post-conditions. The duplication of the deletion statement could have been replaced with lifecycle preconditions or return behavior info.

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 0%, so parameters are completely undocumented at the schema level, and the description does not describe what 'queue_id' or 'model' mean or how they should be formed. The description adds no parameter-level meaning despite the 0% coverage gap, leaving the agent to infer from names.

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 the tool marks a completed video as downloaded and deletes server-side media. It uses a specific verb-action pairing and identifies it as a 'cleanup hook'. It distinguishes from siblings like venice_video_status and venice_video_generate by focusing on the completion/cleanup lifecycle step.

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?

The description implies this is a cleanup hook to be called after downloading a video, and mentions it supports x402 wallet auth and API key. However, it doesn't explicitly state when to use this vs the sibling venice_music_complete or other completion tools, nor does it spell out that it should only be called after the video is fully downloaded.

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