auto_master_music

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

No annotations provided, so description carries full burden. It details background execution, job_id return, and a 6-step pipeline with genre-tuning and optional noise reduction. Explains verify cost and that noise reduction is off by default. Very transparent.

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?

Well-structured with numbered pipeline steps and separate args section. Every sentence is informative with no fluff. Two paragraphs clearly separate behavior from parameters.

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?

Explains async flow and monitoring method. No output schema, but description states returns job_id. Could mention output file retrieval but the flow is clear. Complete enough for an async mastering tool.

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 has 0% description coverage. Description fully explains each parameter: style with an enum list, noise_reduce with default and recommendation, verify with cost warning. Adds critical context beyond schema types and defaults.

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 masters music tracks with genre-tuned settings, using the verb 'master' and resource 'music track'. It distinguishes itself from sibling auto tools by describing a specific pipeline and async behavior returning a job_id.

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?

Explicitly warns not to call again if a pipeline is already running, directing to check_pipeline_status. Provides pipeline steps but does not explicitly compare to manual alternatives. The instruction is strong enough for basic usage.

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