Master and Record Manifest Delivery

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

Given all annotations are false, the description bears full responsibility. It discloses two-pass processing, risk reporting, and atomic provenance recording, but omits whether the source is modified, permission requirements, or potential side effects. The term 'master' implies potential overwriting without clarification.

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 a single sentence that packs three major actions without redundancy. It is dense but not verbose. A more structured format (e.g., bullet points) could improve readability, but current conciseness is acceptable.

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?

With an output schema present, return values are documented elsewhere. The description covers core functionality but lacks context on input prerequisites (e.g., existence of manifest), expected workflow order, and what 'two-pass' entails. Missing guidance makes the tool less self-contained.

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 low (44%), and the description does not compensate by explaining key parameters like target_lufs, expected_revision, or target_true_peak_dbfs. While the overall process is described, the meaning and interplay of numeric parameters remain unclear, leaving the agent to guess optimal values.

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 identifies the tool's purpose: performing two-pass loudness mastering on a current mix/master, reporting risk metrics, and recording provenance. The combination of specific verb ('loudness-master') and resource ('current mix/master') clarifies intent, though the domain-specific acronyms (LRA) may reduce clarity for unfamiliar agents.

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?

No explicit guidance on when to use this tool versus alternatives like vocaloid_render_manifest_master or vocaloid_render_stem_mix. The description implies final delivery context but does not state prerequisites, exclusions, or preferred scenarios. Sibling tools suggest overlapping functionality, making differentiation unclear.

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