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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial beyond-schema behavior: output is an audio content block, failures are not charged, first call is free, and the exact retry mechanism. This is exactly the kind of payment/auth/return-shape context an agent needs before invoking.

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 core purpose and limits are front-loaded and the description is dense with useful facts. It is slightly over-packed and repeats the price twice ('$0.001 USDC per started 1,000 characters' and 'Price: $0.001 per started 1,000 characters'), costing a little conciseness.

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 compensates by naming the return format (WAV audio content block) and detailing the payment handshake. For a 4-param, single-required tool, an agent has everything needed to call it and handle the payment retry.

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 coverage is decent (75%), and the description supplements it with the language set, the 400-char MCP cap, and how x402_payment/_meta payment must be supplied on retry. The idempotency semantics of requestKey are spelled out in the schema rather than the description, leaving a minor gap.

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 opens with a precise verb+resource ('Text to speech / TTS / voice generation (MeloTTS)') and states the exact input languages and output form (WAV voice clip as an audio content block). This clearly separates it from siblings like speech_to_text and text_to_speech_demo.

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?

It gives concrete operating context: 400-char limit per MCP call, 2,000 via REST, and the two-step x402 flow (first call returns PaymentRequired, retry with payment in _meta['x402/payment']). It does not explicitly say when to prefer it over text_to_speech_demo, so it stops short of full alternative routing.

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