Venice Music Queue

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

No annotations provided, so description carries full burden. Discloses it is queue-based, returns queue_id, supports NSFW and auth methods, and suggests polling with venice_music_status. Lacks details on rate limits or destructive behavior but is otherwise transparent.

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 sentences with clear front-loading: purpose, models, additional context. No fluff, every sentence adds value.

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 5 parameters, no output schema, and no annotations, the description covers purpose, models, auth, return type, and polling. Lacks explanation of optional parameters and error handling, but is generally complete for a queue-based tool.

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 coverage is low (20% - only model has description). Description lists models and mentions return format but does not explain lyrics, instrumental, or duration_seconds parameters. Adds value but insufficient to compensate for missing schema descriptions.

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 'Queue music generation' and lists available models, making the verb and resource explicit. Distinguishes from siblings like venice_music_status and venice_music_complete by specifying it is for queuing generation.

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?

Implies usage for generating music but does not explicitly state when to use it vs alternatives like venice_music_complete. Provides some context (NSFW allowed, auth methods) but no when-not-to-use.

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