media_transcribe

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

With no annotations, the description carries the burden of behavioral disclosure. It does add meaningful transparency by explaining the backend resolution order (faster_whisper then openai-whisper) and the clear error behavior when dependencies are missing. However, it omits other behavioral traits such as output format, model download behavior, or potential latency, so it is only average.

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 exceptionally concise and well-structured. The first sentence states the core purpose, and the second sentence provides necessary operational detail about fallback behavior and error handling. Every word contributes value, with no redundancy or filler.

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 output schema and complete parameter descriptions, the description covers the key operational aspects needed for a moderate-complexity tool: the offline requirement, backend fallback ordering, and failure mode. It lacks sibling differentiation and explicit usage context, but it still provides sufficient information for an agent to select and invoke the tool correctly in most situations.

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 has 100% coverage with clear descriptions for all three parameters (file_path, model, language). The description does not add any extra meaning beyond what the schema already provides, 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 the tool's purpose: transcribing speech in a media file with Whisper. It identifies the specific action (transcribe) and resource (media file), and the mention of Whisper gives a concrete method. However, it does not distinguish itself from the closely related sibling tool clip_transcribe_audio, so it misses the full differentiation for 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?

The description provides no guidance on when to use this tool versus alternative tools such as clip_transcribe_audio or media_probe. It mentions the offline/optional dependency aspect, which is a usage caveat, but it does not specify when this tool is the appropriate choice or when another sibling should be preferred.

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