Single tool 'aivis-speech' has a well-structured JSON Schema input with proper type definitions and descriptions for all parameters. However, the tool description is in Japanese, which limits accessibility for English-speaking LLM contexts. More critically, there is no documented output schema, the LLM cannot know what fields to expect in the response. The tool is language/locale-specific (Japanese TTS) and lacks error handling guidance, recovery instructions, or examples of what successful responses look like. Parameter descriptions are present and clear (e.g., 'wait_ms' has min/max bounds), but the tool lacks the comprehensive error classification and recovery patterns expected of production-grade tools.
Aivis 音声合成/再生ツール
Tool description is in Japanese only ('Aivis 音声合成/再生ツール'). English-speaking LLMs and internationalized deployments cannot determine when to call this tool.
No output schema documented. LLM cannot know what fields the response contains, making it impossible to plan downstream tool calls or extract results.
No error handling guidance. Tool description does not explain failure modes, recovery steps, or how to interpret errors. Pattern: recovery-guide not followed.
Tool name 'aivis-speech' is not a verb_noun action. Recommended rename to 'synthesize_speech' or 'play_speech' to clarify the action the LLM is invoking.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 41 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 35 | - | v1 |
Parameter 'model_uuid' requires opaque UUID format but accepts no human-readable fallback. Users/LLMs without a UUID must perform extra lookups. Consider accepting both 'model_uuid' and 'model_name' or 'model_alias'.
'sync' parameter semantics are unclear in English. Description says 'waits until playback completes', but does this block the API? Return success immediately? Timeout behavior? Add clarity and timeout guidance.