mimo.asr

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

No annotations exist, so the description carries full burden. It mentions returning plain text and a default model but omits crucial behavioral traits like file size limits, audio format requirements, latency, or auth needs. This is insufficient for safe invocation.

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?

Two sentences, front-loaded with purpose, and every part adds value: first sentence defines the tool, second details parameters and behavior. No wasted 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?

Given the tool accesses files/URLs and has an output schema (returning plain text), the description fails to mention prerequisites, supported formats, or constraints. Critical gaps in completeness for a resource-processing tool.

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 0%, but the description explains that audio_path is for local files, audio_url for direct links, and language accepts options auto/zh/en. This adds context beyond the raw schema, though format details and 'auto' semantics remain vague.

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 '语音转写' (speech transcription) with a specific verb and resource. It distinguishes from siblings like mimo.tts and mimo.chat through its focus on audio-to-text conversion. The hotkey hint (F7) adds specificity.

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 explains the two input modes (local file or URL) and the optional language parameter with default model. While it implies usage for speech-to-text, it lacks explicit exclusions or comparisons to sibling tools, but context is clear enough for an AI.

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