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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the pricing model ($0.012/min + $0.002, $0.014 minimum, $1.443 USDC per call via x402) and a genuine behavioral fork: store=true returns a 7-day share link instead of inline data. That output-mode switch is real context the annotations do not cover, though it does not describe rate limits 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?

Purpose and model lead, features follow, pricing closes. It is dense but every sentence carries information; the repeated dollar figures are slightly heavier than needed but not wasteful.

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 7-parameter tool with no output schema, the description should sketch the return shape; it only hints that store changes inline-vs-link and never explains the base64 input path or required/optional status. Pricing is covered thoroughly, but the calling contract is only partially 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?

Schema coverage is 86% (baseline 3), but the description adds cost semantics for max_minutes ('$0.002 set max_minutes') and clarifies store, diarize, and words beyond their short schema blurbs. It does not address the undocumented audio_base64 parameter, which is the one gap keeping it from a 5.

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 states a specific verb and resource ('transcription ... for a public audio or video file') and names the underlying model (Deepgram Nova-3) plus its feature set. It distinguishes itself from the generic 'transcribe' sibling only by the word 'Premium', which implies a higher tier without explicitly stating the difference, so it falls short of a 5.

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?

Usage is implied rather than stated: the pricing and 'Premium' framing suggest this is the higher-quality, higher-cost option versus 'transcribe', but no alternative is named and no when-to-use/when-not condition is given. An agent must infer the routing decision from cost alone.

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