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

Annotations already declare readOnly/idempotent/non-destructive and a closed (openWorldHint=false) static dataset. The description adds value beyond that by stating the exact metrics returned and clarifying scope (applies to any music, not just the catalog), which tells the agent this is a general-purpose reference lookup.

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?

Four compact sentences, front-loaded with the core purpose before the use cases. Nothing is redundant, though the final scoping sentence could arguably be trimmed.

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 no output schema, the description carries the return-value burden and does so by naming the specific standards (LUFS targets, true peak limit). An agent has enough to invoke and interpret it, though field-level return structure is not spelled out.

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?

The single optional 'platform' parameter is fully documented in the schema (100% coverage) with examples and empty-string behavior. The description adds no parameter detail beyond the schema, so the baseline of 3 is appropriate.

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?

States a specific verb and resource ('Returns the official loudness normalization standards for major music and video platforms') and enumerates what is returned (integrated LUFS, true peak, short-term LUFS). The closing line explicitly distinguishes it from catalog-bound siblings by noting it 'works for any music — not limited to the OnChain Music catalog.'

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?

Gives concrete use contexts: mastering decisions, mix prep, and meeting platform requirements before distribution or licensing. No explicit when-not or named alternative, but no sibling overlaps this static-reference function, so the guidance is clear.

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