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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description still adds meaningful behavioral context by naming the concrete actions it will not take — no quoting, spending, or generating — which is exactly the cost-safety concern for this API family. It omits rate limits, auth requirements, and freshness/latency caveats.

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?

Two sentences, zero waste: the positive enumeration is front-loaded and the negation is deferred to second position. Nothing is padded or restated from the schema.

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 enumerating the returned categories, which is adequate for a zero-parameter discovery tool. The phrase 'confirmation contract' is left somewhat abstract, and there is no guidance on whether the result is cached or versioned.

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?

Zero parameters, so there are no argument semantics to document and the baseline is 4. The description correctly implies the tool is called with no arguments.

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 ('Lists') and enumerates the exact resource contents (Audio modes, settings, reference roles, provider availability, pricing revision, confirmation contract). The negative scope ('does not quote, spend, or generate') implicitly separates it from pricing and generation siblings, but no sibling is named explicitly.

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 supplies exclusions ('does not quote, spend, or generate') which is useful when-not guidance, but never states when an agent should call this versus list_models, get_model_details, or prepare_audio_generation. Usage is only implied.

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