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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description still adds real value by disclosing the side effect that output is persisted to the user's Xenition library and returned as an MP3 link — a lasting artifact an agent should know about.

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?

A single tight sentence with the trigger front-loaded and the return/persistence behavior trailing. Every clause earns its place; nothing is redundant with the title or 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?

An output schema exists, so return-value detail is not required, yet the description still summarizes it as an MP3 link. For a non-destructive creation tool with full annotations, the trigger plus persistence note is sufficient, though it omits any hint about voice/language options or generation latency.

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 75% (text, voice, and language are documented; title is not). The description adds no parameter-level meaning at all — nothing about voice selection, language codes, or what title does — so it neither compensates for the gap nor improves on the schema. Baseline 3 for high coverage.

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 states a concrete verb and resource — turning text into an audio file — and illustrates it with use cases (voiceover, narration, spoken message). It is clearly distinguishable from the inverse sibling transcribe_audio, though it never names any sibling 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?

"Use this when the user wants text read aloud as an audio file" gives an explicit triggering condition. There is no statement of when not to use it and no alternative tool is named, so it stops short of full routing guidance.

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