voicebox_delete_model

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

The description indicates a destructive action (deleting from disk) but does not explicitly state that the operation is irreversible or whether there are prerequisites (e.g., model must be downloaded but not loaded). No annotations are provided, so the description carries the full burden, but it does not fully articulate behavioral traits.

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 sentence of 9 words, front-loaded with the action. Every word is necessary, and there is no extraneous information.

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 simple delete operation, the description covers the basic purpose but omits context like whether the model must be unloaded first, what happens if the model is in use, or how to check which models are downloaded. An output schema exists but is not shown; however, the description could be more complete.

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 100% for the single parameter 'model_name', and the description does not add any extra semantic meaning beyond what the schema already provides. Baseline 3 is appropriate.

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?

Description clearly states the verb 'Delete', the resource 'downloaded model', and the reason 'to free space'. It distinguishes from sibling tools like unload_model (which unloads from memory) and delete_version (which deletes a version, not the model itself).

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 the tool is for freeing disk space by deleting a downloaded model, but it does not explicitly state when not to use it or mention alternatives like unload_model for memory-only removal. The guidance is minimal.

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