mm_synthesize_speech

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

Annotations indicate non-read-only and non-destructive behavior. The description adds that the tool saves to MP3 and returns an absolute path, which gives concrete side-effect information beyond the annotations. It does not contradict annotations and offers useful behavioral context.

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 description is a well-structured docstring with a concise purpose statement followed by Args and Returns sections. Every element serves a purpose, with no unnecessary wording. It is front-loaded with the core functionality.

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?

The description covers the essential input parameters, defaults, and return type, making it sufficient for a simple TTS tool. Minor gaps remain, such as overwrite behavior and a list of supported voices, but the description is largely complete for typical use.

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?

With 0% schema description coverage, the description compensates by explaining each parameter: text (max 1000 chars), voice (default zh-CN-XiaoxiaoNeural), and output_path (default outputs/audio/). This adds practical meaning, though it leaves some ambiguity about whether output_path is a directory or full file path.

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 clearly states the tool's function: '把文字合成为语音并保存为 MP3' (synthesize text into speech and save as MP3). This specifies a distinct action (synthesis) and output format, distinguishing it from sibling tools like mm_transcribe_audio (inverse task) and mm_generate_image/video.

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?

The description provides practical constraints (max 1000 characters) and defaults (voice, output path), which imply when to use the tool. However, it does not explicitly mention alternatives or when not to use it, leaving usage guidance implied rather than explicit.

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