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

Beyond the annotations (which already declare readOnly/destructive/idempotent), the description discloses cost behavior the annotations cannot convey: $0.003/call, payment via x402 USDC or card key, failed calls free, and the practical consequence that repeats are billed. It also confirms the tool changes nothing, aligning with readOnlyHint.

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?

Purpose and output format are front-loaded in the first sentence, with usage, example, and pricing following in a logical order. It is dense and every sentence carries information, though the pricing/billing clause makes it longer than strictly minimal.

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 specifying the return format (base64 audio plus content type). Combined with the character limit, language options, usage guidance, and billing model, an agent has everything needed to call it correctly.

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 description coverage is 100%, so both parameters (text, lang) and the enum values are already documented. The description's example (text=..., lang=en) reinforces usage but adds no syntax or constraint meaning beyond the schema's 1,000-character limit and language list, so baseline 3 applies.

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 transformation (text into natural speech as an audio file), names the engine (MeloTTS), the exact output encoding (base64 with content type), and the supported languages. It is clearly distinguishable from the inverse sibling 'transcribe' and from generic AI siblings.

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?

Explicitly lists target use cases (voice replies, audio notes, accessibility, phone/chat bots) and provides a concrete invocation example, so the agent knows when this tool fits. It stops short of naming alternatives or stating when NOT to use it (e.g., preferring 'transcribe' for the inverse direction).

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