auto_audiobook_mastering

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

With no annotations, the description carries the full burden of behavioral disclosure. It provides valuable transparency: the tool runs in background, returns a job_id immediately, and requires monitoring through check_pipeline_status. It also details the exact processing pipeline, target RMS/peak values, and the important remove_noise caveat about the first 0.5s needing room tone. However, it does not specify what audio is processed (e.g., selected clips, all tracks, whole project) or whether the operation is destructive/reversible, which is a meaningful gap.

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 well-structured and information-dense without padding. The all-caps headline, pipeline breakdown, target specifications, and Args section each add necessary operational detail. Every sentence contributes value, and the most critical warnings are called out prominently.

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 background job tool with no output schema, the description explains the asynchronous behavior, the returned job_id, and the monitoring tool to use. It also covers the main argument and the processing targets. The main missing context is the input scope — what audio the mastering applies to — which could be important for an agent deciding whether to invoke this tool on a given project.

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%, but the description fully compensates for the single parameter. It explains remove_noise applies noise reduction using the first 0.5s as a noise profile, states the default is True, and highlights the important prerequisite that the first 0.5s should be room tone/silence if enabled. This is substantially more meaning than the bare boolean schema field provides.

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 states a specific verb and resource: 'ONE-CLICK AUDIOBOOK MASTERING: ACX/Audible compliant processing.' It clearly identifies the purpose and differentiates it from sibling tools like auto_master_music or auto_cleanup_audio by specifying audiobook/ACX compliance rather than general music mastering or cleanup.

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?

The description clearly indicates when to use this tool: for one-click audiobook mastering targeting ACX requirements. It also gives workflow guidance by noting it runs in the background and instructing the user to use check_pipeline_status to monitor. It does not explicitly list when not to use it or name alternatives, but the context is clear enough to guide selection.

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