audio_transcriber_initiate_streamStarts the audio input stream so you can capture microphone audio for transcription. Use it to begin recording before sending audio to the transcriber.
Initiate the audio input stream.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.3.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, implying an external-resource setup step, but the description adds nothing beyond that — no mention of device permissions, resource allocation, or what happens if a stream is already open. Given the openWorld hint, the description should clarify the side effects of opening an external capture stream.
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?
It is a single short sentence with no wasted words and is front-loaded, but the brevity comes at the cost of under-specification rather than genuine efficiency.
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 stateful stream-lifecycle tool with no parameters and no output schema, the description leaves the agent without the essential context: what the stream captures, what state changes occur, and which sibling to call next (stop_stream/save_stream). It is not complete enough to call correctly with confidence.
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?
The tool takes zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description does not mislead about inputs.
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 says 'Initiate the audio input stream', which gives a verb and a resource, but the resource is only vaguely identified — it is unclear whether this opens a microphone, a file, or a network stream. It does not distinguish this from siblings like audio_transcriber_record or audio_transcriber_stop_stream.
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 indication of when this tool should be used instead of audio_transcriber_record, nor any mention of the required follow-up (stop_stream / save_stream). The agent must infer the whole stream lifecycle from sibling names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.