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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the return format (base64 audio as the model gives it), an infrastructure prerequisite (env.AI binding), and a full cost model ($0.003 USDC per successful call via x402 on Base/Solana/Arc, failures not charged). These are exactly the operational facts an agent needs before invoking a paid endpoint.

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?

Four tight sentences, front-loaded with the core action and followed by return format, exclusions, and pricing. Every sentence carries information, though the pricing/dependency clause could be compressed slightly.

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 an output schema present, the description need not explain return values, yet it still notes base64 audio. Language limits, input bound, dependency, and billing are all covered, leaving nothing an agent needs missing.

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) are already documented in the schema, and the description merely restates the character limit and language set. Baseline 3 applies because the schema does the heavy lifting.

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-and-resource statement ('Turns text ... into speech with a Cloudflare Workers AI TTS model') and enumerates the supported languages, making it clearly distinguishable from the inverse sibling agent_intel_speech_to_text_transcribe_turbo.

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 states concrete operating bounds (up to 1000 characters) and explicitly excludes German and Turkish with a reason, which steers the agent away from unsupported inputs. It does not name an alternative tool for when TTS is the wrong choice, so it falls short of a full when/when-not/alternative statement.

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