process_audio

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

The description discloses the output file path and the processing operations, providing some behavioral context. However, with no annotations, it omits details like whether the tool is destructive, required permissions, or error behavior.

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 that wastes no words. However, it is under-specified for the tool's complexity, missing parameter guidance and usage context.

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 no schema descriptions, no annotations, and three parameters, the description is incomplete. It omits parameter semantics, usage guidelines, and does not leverage the output schema to clarify behavior.

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?

The description does not explain any of the three parameters (strength, project_id, target_lufs). With 0% schema coverage, the description adds no meaning beyond the schema, leaving the agent to guess parameter roles.

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 specifies the tool's function: denoising, enhancing vocals, and applying loudnorm normalization, and identifies the output file 'audio/vocals_clean.wav'. This distinguishes it from sibling tools like mix_bgm or transcribe_and_caption.

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., apply_recipe or mix_bgm). The description lacks context about prerequisites or scenarios where this tool is preferred.

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