Transcribe Audio / Video with Whisper

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which are consistent with the description (creates a prediction, not destructive). The description adds details on return format (PredictionResult with text_output), timeout behavior (returns prediction ID if exceeded), and model options, providing context beyond annotations.

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 and front-loaded with the main purpose. It lists parameters clearly without redundancy. It could be slightly more structured (e.g., separating description from args), but it is efficient and focused.

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 complexity (7 parameters, nested objects, no output schema), the description covers the return type, timeout behavior, and optional parameters. It does not specify file size limits or supported formats, but these are likely implied by the Replicate platform.

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?

With 86% schema coverage, the baseline is 3. The description adds value by explaining the model parameter (curated keys vs 'owner/name'), the translate_to_english boolean, and the extra_input object for model-specific options, which supplements the schema descriptions.

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 'Transcribe an audio or video file to text using Whisper-family models on Replicate', with a specific verb (transcribe) and resource (audio/video to text). It distinguishes itself from sibling tools like replicate_generate_speech (text-to-speech) and replicate_vision (image processing).

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 transcription tasks and explains parameters like model selection, language hint, and translation. However, it does not explicitly mention when not to use this tool (e.g., for real-time transcription) or compare to alternatives like replicate_run_model with custom models.

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