Convert text into spoken audio on your Android phone using built-in TTS, with optional language selection. Use it when an assistant needs to read messages, alerts, or answers aloud.
Speak text out loud on the phone (TTS).
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| language | No | e.g. en, ru, cs |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full behavioral burden. It discloses only the output modality (audio TTS on the phone); it says nothing about whether the call blocks until speech finishes, whether it requires an active phone connection, or what happens on failure.
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 short sentence with the key mechanism front-loaded and no wasted words. It is efficient, though its brevity is part of why behavioral and parameter detail is missing.
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 simple two-parameter tool with no output schema, the description is minimally adequate to identify the action. However, with no annotations and an undocumented required parameter, an agent lacks enough context about side effects and defaults to invoke it confidently.
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 coverage is 50%: 'language' has an example list but 'text' is undocumented. The description adds no meaning to either parameter, such as length limits, expected format, or what happens when language is omitted (default voice?).
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 gives a specific verb ('Speak') and resource ('text out loud on the phone') and clarifies the mechanism with '(TTS)'. It does not distinguish itself from siblings such as notify, which could plausibly also emit user-facing output, so it stops short of a 5.
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?
There is no guidance on when to use this tool versus alternatives like notify, nor any stated preconditions (e.g. phone connected, audio available). The agent must infer usage entirely from the one-line purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.