auto_cleanup_vocal

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

With no annotations, the description carries the full behavioral burden. It discloses background execution, immediate job_id return, the complete processing pipeline, the 0.5s noise-profile requirement, and a concurrency guard. This is unusually transparent for a cleanup tool.

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 dense but well-organized: purpose first, then execution model, pipeline, parameter detail, and guardrails. Every sentence adds operational value, and the all-caps labels highlight the highest-signal constraints.

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 tool with one optional boolean parameter, no output schema, and no annotations, the description covers the return contract (job_id), monitoring path, parameter semantics, and concurrency rules. Nothing needed to make a correct first call is missing.

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%, so the description must compensate. It explains that remove_noise applies noise reduction using the first 0.5s as a noise profile, and the IMPORTANT note adds the precondition that those first 0.5 seconds should be room tone or silence when true. This is critical meaning not present in the schema.

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 opens with 'ONE-CLICK VOCAL CLEANUP: Professional processing for singing and studio vocals,' which is a specific verb and resource. 'Tuned for singing' distinguishes it from sibling cleanup tools like auto_cleanup_podcast or auto_cleanup_interview, so an agent can route correctly.

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?

It explicitly names check_pipeline_status for monitoring and warns 'DO NOT call this again if a pipeline is already running — use check_pipeline_status instead,' giving a clear when-not and alternative. 'Tuned for singing' also signals the intended use case versus other cleanup variants.

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