list_audio_models

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

The annotations already declare this as read-only, idempotent, non-destructive and open-world, so safety is covered. The description adds useful return-content context by specifying that it surfaces speech, music and sound effect model IDs, voices, supported parameters and customer credit prices, though it does not describe output structure or pagination.

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 front-loaded sentence that immediately states the discovery action and enumerates the returned information. Every element earns its place, and there is no redundant or filler 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?

For a zero-parameter read-only catalog tool with no output schema, the description gives an adequate account of the categories of data returned. It could be stronger by clarifying the relationship to sibling catalog tools or the exact shape of the pricing and parameter information, but it is broadly complete.

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?

There are no input parameters, so there is nothing for the description to clarify beyond the zero-parameter baseline. The description correctly does not waste space discussing nonexistent 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 uses a specific verb, 'Discover', and names the resource precisely: speech, music and sound effect model IDs, voices, supported parameters and credit prices. This is clear enough to understand the tool's function, but it does not explicitly differentiate it from sibling tools such as list_models or get_capabilities.

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 that this is a pre-generation discovery tool by listing model IDs, voices, parameters and prices, but it never states when to use it versus alternatives like list_models, get_capabilities or quote_audio. Usage is inferable from context rather than explicitly guided.

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