auto_audiobook_mastering

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

Details async background processing, return of job_id, side effects of verify parameter (extra exports), and the required silence for remove_noise. With no annotations, description fully covers behavioral traits.

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 bold heading, pipeline list, parameter args, and important notes. Front-loaded with purpose. Slightly verbose but every sentence adds value.

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?

Complete for a 2-parameter async tool: explains return value (job_id), monitoring via sibling, parameter details, and prerequisites (room tone). No output schema needed given description.

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?

Adds significant meaning beyond schema: explains remove_noise uses first 0.5s as noise profile and verify measures before/after with cost. Schema coverage is 0%, so description compensates fully.

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?

Clearly states 'ONE-CLICK AUDIOBOOK MASTERING: ACX/Audible compliant processing' and lists pipeline steps. Distinguishes from sibling auto tools like auto_cleanup_audio by specifying ACX compliance and background job behavior.

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 says to use check_pipeline_status for monitoring and warns not to call again if pipeline is running. Provides context for when to use (ACX compliance) but does not mention alternatives among siblings.

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