deepgram_transcribe

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that the tool returns transcript, confidence, and word-level timestamps, and seals a ProofLink receipt. However, it does not disclose potential side effects, authentication requirements, rate limits, or supported audio formats.

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, consisting of three sentences that efficiently convey the action, output, and a side effect. Every sentence adds value without redundancy.

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 simple tool with two parameters, no output schema, and no annotations, the description covers the key functionality and return values. However, it lacks information on supported audio formats, error handling, and behavior when both parameters are provided. The mention of 'ProofLink receipt' is intriguing but not explained.

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% (both parameters are described in the input schema). The description adds no further detail beyond what the schema states (URL and file path). According to the baseline rule, a score of 3 is appropriate since the schema already covers the parameters adequately.

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 that the tool transcribes audio using Deepgram Nova-2 from a URL or file path. It distinguishes itself from sibling tools like deepgram_tts (text-to-speech) through the transcription function, but does not explicitly differentiate from all 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 provides no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites, limitations, or scenarios where it should not be used. The context of siblings (e.g., deepgram_tts) is not leveraged for differentiation.

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