Master an audio track (AI mastering)

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

Discloses synchronous nature with internal polling and expected time (30s-5min), cost (20 credits, free for higher plans), output format (WAV, ~50MB), and lossless quality. Annotations already present; description adds significant context.

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?

Efficient single paragraph that front-loads key action and time expectation, then provides usage context, cost, output, and preset guidance. Every sentence adds value without redundancy.

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?

Adequately covers return value (mastered URL), output format, and size. With no output schema, description explains what agent receives. Slightly missing explicit response structure but sufficient for a straightforward 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 coverage is 100% with descriptions. Description adds value by explaining preset steers style, recommends calling list_presets for details, and lists examples. TrackTitle context ('used in gallery row label') is extra.

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 it submits audio for AI mastering and returns a mastered URL. Distinguishes from siblings by noting it's a final polish step after music generation and references aetherwave_list_master_presets. Specific verb and resource.

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 'Useful as a final polish step after music generation,' implying when to use. Does not give explicit when-not-to-use but provides context on cost and plans. References sibling tool for preset selection.

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