auto_master_music

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

With no annotations provided, the description carries the full transparency burden, and it does so thoroughly. It discloses that the tool runs in the background and returns a job_id, details the pipeline order and defaults, lists concrete genre loudness targets, explains the clip-safe fallback, and warns about the counterintuitive quieter-if-already-loud behavior. There is no contradiction with annotations because none exist.

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 front-loaded with the tool's purpose and async behavior, then provides necessary pipeline and loudness-target detail. It is longer than minimal, but the complexity of a mastering pipeline justifies most of that length. The 'see _mastering_pipeline's docstring for sources' aside and some marketing phrasing add minor noise, but overall it remains well-structured.

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 no output schema and no annotations, the description covers the essential invocation details: both parameters with defaults, the job_id return, the monitoring path, pipeline stages, loudness targets, and the quieter-than-input caveat. It does not explicitly state how the target track is selected before calling or describe failure/error handling, but it is close to self-sufficient.

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 for the bare schema. It explains both parameters: style is a genre preset with the six accepted values and a default, and noise_reduce is a gentle noise-reduction toggle defaulting to false. This adds real semantic meaning beyond the schema's type/default declarations.

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 MUSIC MASTERING' and clearly states the tool's job: professionally master a music track with genre-tuned settings toward a published loudness target. This distinguishes it from peak-limiting-only tools and from the audiobook/podcast cleanup siblings. The verb, resource, and intent are immediately unambiguous.

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 establishes clear context: use this when you want automatic, one-click music mastering aimed at genre-specific loudness rather than just peak limiting. It also explains the async workflow and directs the agent to check_pipeline_status for monitoring. It does not explicitly name alternative tools for manual mastering or podcast/audiobook cleanup, so it stops short of a 5.

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