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

No annotations are provided, so the description carries full burden. It describes the return output (deviation analysis with suggestions) but does not explicitly state whether the tool is read-only or has side effects. The example gives a sense of output structure.

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 concise and well-structured with a short intro, bullet points for analysis dimensions, parameter documentation, return clarification, and an example. No redundant text.

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?

Given the existence of an output schema, the description provides a good overview of return structure. It covers the main use case, parameter ranges, and an example. However, it does not mention error conditions, file size limits, or prerequisites beyond file path.

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%, so the description adds significant value: it documents the 'filename' parameter as a WAV file in exports or absolute path, and lists all valid genres for the 'genre' parameter. This goes beyond the bare schema.

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 states the tool compares a mix against a genre profile, listing specific dimensions (LUFS, spectrum, stereo width, dynamics, spectral centroid). It effectively distinguishes from siblings like 'compare_to_reference' which is for comparing to a specific reference track.

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 implies when to use: when you need to see deviations from genre standards. It implicitly distinguishes from alternative sibling tools but does not explicitly state when not to use it.

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