voicebox_delete_profile

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

The description adds that samples are deleted, but for a destructive operation without annotations, it fails to disclose irreversibility, cascading effects on generations or stories, authorization requirements, or error handling.

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?

Single sentence with no redundant words. Perfectly concise for a simple delete operation.

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 the presence of an output schema, return values are not required. However, for a delete tool, the description lacks important context about success indicators, error states, and consequences beyond the profile and samples.

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 100% with a clear description. The tool description adds no extra meaning to the parameter beyond stating the overall effect. 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?

The description clearly states the action 'Delete' and the resource 'voice profile', and specifies the additional consequence of deleting all samples. This distinguishes it from sibling deletion tools like voicebox_delete_version or voicebox_delete_capture.

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., voicebox_delete_sample for partial deletion). Prerequisites (e.g., profile existence) and when-not-to-use scenarios are absent.

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