save_voice

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

With no annotations, the description takes on full burden. It discloses that the tool saves to disk, optionally transcribes (requiring OpenAI API key), returns transcript inline, and lists error codes. Missing details on failure handling or overwrite behavior, but overall transparent.

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 concise (4 sentences) and front-loads the core purpose. It is efficient but could be slightly more structured, though it remains easy to read.

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 7 parameters, no output schema, and no annotations, the description covers purpose, optional transcription, and error codes, but lacks details on return values beyond transcript inline and does not provide example usage. It is adequate but leaves gaps for an AI agent.

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 low (29% - only timeoutMs and transcribe have descriptions). The description adds meaning by mentioning transcribe:true and the same parameter contract as save_image, but does not explain chatId, msgId, folder, filename, or skipIfExists beyond the schema. Reliance on another tool's description is insufficient.

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 tool saves voice notes (.ogg) to disk and optionally transcribes them. It references save_image as a similar tool, helping differentiate from image saving but not from save_media or other siblings.

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 voice notes and when transcription is needed, but does not explicitly state when not to use it or recommend alternatives. The reference to save_image provides some context but lacks clear when-to or when-not-to guidance.

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