voicebox_download_cuda

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

With no annotations, the description only says 'download and install,' failing to disclose potential side effects (e.g., disk usage, network dependency, time required) or whether it is destructive.

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 a single concise sentence containing all necessary information with no wasted words.

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 potentially lengthy installation tool, the description omits important context like progress monitoring (via sibling tools), output schema, or behavior during failures. The lack of detail leaves the agent underinformed.

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?

There are no parameters, so the description inherently covers them. Baseline 4 is appropriate as no additional meaning is needed beyond what the schema conveys.

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's verb ('Download and install') and resource ('CUDA backend support for GPU acceleration'), distinguishing it from sibling query tools like voicebox_get_cuda_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?

No guidance is provided on when to use this tool versus alternatives (e.g., checking status first, prerequisites, or typical workflow).

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