deepgram_tts

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

Since no annotations are provided, the description carries the full burden. It discloses side effects: saving to a specific folder and sealing a ProofLink receipt. It also names the voice model. However, it does not mention rate limits, authentication needs, or failure behavior.

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?

Single sentence with three concise clauses. No redundant words, efficient communication of key aspects: action, model, output location, receipt, and return value.

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's simplicity and full parameter schema coverage, the description covers return value (mp3_url) and side effects (saving, sealing). Lacks details on error handling or constraints, but those are partly in schema (max 4000 chars). Still sufficient for basic usage.

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 100% (all three parameters have descriptions). The description does not add significant new meaning beyond what is in the schema; it repeats the default voice name already documented. Baseline 3 is appropriate.

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 action ('Convert text to speech'), the specific resource ('Deepgram Aura (aura-asteria-en)'), and the output (MP3 saved to mission-videos/, returns mp3_url). It is distinct from sibling tools like deepgram_transcribe (transcription) and deepgram_blog_audio.

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?

No explicit guidance on when to use this versus alternatives (e.g., other TTS models or methods). The description does not mention exclusions, prerequisites, or context-dependent selection criteria.

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