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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds substantial non-derivable behavior: per-call pricing of $0.005 USDC via x402 on Base, free errors, the content-refusal policy with HTTP 400 and no charge, the 2000-char limit, and the default no-param sample behavior.

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?

Dense but front-loaded: pricing and the core transform lead, then output formats, use cases, refusal policy and defaults. Every sentence carries information, though the parenthetical-heavy phrasing makes it slightly harder to scan than it could be.

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?

There is no output schema, and the description compensates fully by specifying the return shape (JSON with audio_base64 + mimeType audio/wav, 44.1 kHz mono) or raw bytes with format=wav. Pricing, refusal behavior, defaults and transport are all covered, so an agent can call this correctly without further context.

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 100%, so baseline is 3, but the description adds real meaning: the 2000-char cap, the fact that both params are optional and default to a short English sample, and the GET-query-params vs POST-JSON-body invocation styles. It also references a 'format=wav' option that does not appear in the schema, a small inconsistency.

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+resource ('Turn text ... into spoken audio'), names the engine (MeloTTS on Cloudflare Workers AI) and the six supported languages. No sibling tool does text-to-speech, so the purpose is unambiguous at a glance.

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?

Gives concrete use cases (voice replies, narration, accessibility, language practice) which tell the agent when this tool fits. It does not state when NOT to use it or point at an alternative, but no sibling overlaps, so the omission is minor.

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