Venice Video Complete (cleanup)

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

Explicitly states the destructive action of deleting server-side media, which is critical. No annotations provided, so description carries full burden. Lacks details on irreversibility or scope of deletion.

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?

Two sentences, no filler. First sentence states purpose and side effect, second adds auth context. Efficiently front-loaded.

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?

Given destructive nature, no output schema, and 0% schema coverage, the description is incomplete. Lacks parameter details, consequences, and any usage examples or warnings.

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 has 0% description coverage, and the description does not explain the parameters ('model' and 'queue_id') beyond their names. Adds no value over 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?

Clearly states the action ('Mark a completed video as downloaded') and the side effect ('deletes server-side media'). Distinguishes from sibling tools like venice_video_generate and venice_video_status.

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?

Mentions supported auth methods (x402 wallet and API key), providing context for when the tool can be used. However, no explicit guidance on when to use vs. alternatives or prerequisites.

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