synthesize

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

The description adds behavioral context beyond the schema by mentioning the model architecture, sample rate, and that it returns the output file path and duration. However, it does not disclose potential side effects like file overwriting or failure modes.

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 single sentence that efficiently communicates the main function and output. No unnecessary words.

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?

For a tool with 3 parameters and no output schema or annotations, the description provides essential information about model and output but misses details on error handling, timing (synchronous/asynchronous), and dependency on model preloading.

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 baseline is 3. The description does not add extra meaning for parameters beyond what the schema already provides (e.g., default values, range hints). The return info is useful but not parameter-specific.

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 verb 'synthesize' and the resource 'speech from text', specifies the model (VoxCPM2) and output format (WAV, 48 kHz). It distinguishes from sibling tools like 'synthesize_with_clone' by its focus on standard TTS.

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 implies usage for text-to-speech synthesis but does not explicitly state when to use this tool versus alternatives like 'synthesize_with_clone' or prerequisites like model preloading. The sibling names provide clues, but no direct guidance is given.

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