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

The annotations already indicate a safe read-only operation (readOnlyHint: true, destructiveHint: false). The description adds useful context about what information is returned (credit cost, tracks produced, language coverage), but it does not disclose additional behavioral traits such as pagination, rate limits, or authentication requirements. This matches the baseline for a read-only list tool.

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, well-structured sentence that is front-loaded with the core purpose ('List the music models') and immediately provides the key details of what is included. There is no redundant or extraneous information.

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?

For a zero-parameter, read-only list tool with no output schema, the description is sufficiently complete. It names the resource and explicitly enumerates the main return fields (credit cost per task, tracks produced per task, language coverage), giving the agent a clear expectation of what the result contains.

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 tool has zero parameters, and the schema is empty with 100% coverage by definition. The description does not need to explain parameters, and the baseline score for zero parameters is 4. It appropriately focuses on the output rather than inputs.

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 action ('List') and the resource ('music models available through the API'), and explicitly distinguishes it from sibling tools like generate_music and get_generation by focusing on listing available models rather than creating or retrieving generations.

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 the tool is used to see available models and their metadata, but it does not explicitly state when to use it versus alternatives. For instance, it does not mention 'Use this before generate_music to select a model.' The context of sibling tools suggests usage, but there is no direct guidance.

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