deepgram_transcribe

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

With no annotations, the description carries the burden of disclosing side effects and output behavior. It does mention returning transcript, confidence, and timestamps, and it states 'Seals a ProofLink receipt,' which is a notable side effect. However, it does not discuss permissions, reversibility of the receipt, error handling, or any rate limits, leaving gaps in full behavioral transparency.

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 three short, front-loaded sentences. The main purpose is stated first, followed by the return values and the side effect. Every sentence provides distinct information with no fluff or repetition.

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 tool with two optional parameters and no output schema, the description covers the main aspects: purpose, input modes, return fields, and a side effect. It does not clarify what happens if neither parameter is provided, but given the simplicity and the schema's explicit optionality, the description is reasonably complete.

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 input schema provides 100% coverage with descriptions for both parameters (audio_url and audio_file_path). The description adds no new meaning beyond restating that audio can come from URL or file path, so the baseline score of 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 a specific verb ('Transcribe'), resource (audio), and method ('using Deepgram Nova-2'). It differentiates from siblings like deepgram_tts (text-to-speech) by focusing on speech-to-text and the unique side effect of sealing a ProofLink receipt.

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 use case is implied by the verb 'Transcribe', but the description does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. Sibling tools such as deepgram_tts are clearly different, but no guidance is given for choosing between them.

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