Venice Music Complete (cleanup)

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the bar is lower. The description still adds real value beyond them: it names what is destroyed ('server-side media'), gives a success-confirmation contract ('reports removal only when Venice confirms success'), and discloses auth modes (x402 wallet or API key).

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?

Three short sentences, the destructive action and its effect front-loaded, followed by the confirmation contract and auth options. No filler.

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?

Behaviorally solid for a destructive mutation with no output schema, but with 0% schema coverage on two required params the description should have explained queue_id/model matching semantics. The tool is callable, but an agent could easily pass the wrong model and misfire a destructive operation.

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% for two required parameters, so the description carries the full burden and largely fails it. It never explains what queue_id identifies or whether 'model' must match the model used at generation time, which is a real ambiguity for a destructive call.

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?

States a precise verb and resource: 'Mark a completed music job as downloaded and delete server-side media.' It is unambiguously distinct from venice_music_generate, venice_music_status, and the video equivalents in the sibling list.

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 precondition 'a completed music job' implicitly routes the agent to check status (venice_music_status) before calling, and the name signals it is a terminal cleanup step. No explicit when-not or named alternative is given, so it stops short of a 5.

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