transcribe_audio

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions upload and return of a job_id but lacks details on whether the operation is asynchronous, file deletion policies, authentication needs, rate limits, or response structure. This is insufficient for a mutation-like tool.

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 short (two sentences) and front-loaded with the main action. It covers essentials without fluff. Could be slightly improved by separating formats and return value for clarity, but it's efficient.

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?

There is no output schema, so the description should clarify the return value. It states 'Returns a job_id' but does not explain that the transcription is asynchronous or that job_id is used to poll status. Given siblings like get_job_status, the workflow is partially implied but could be more explicit.

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 100% for both parameters, so the description adds minimal extra meaning for parameters. The description does provide context about the overall action and supported formats, but not beyond what the schema already conveys. Baseline 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 specifies that the tool uploads a local audio/video file to FreeAudioToText for transcription and returns a job_id. It lists supported formats and distinguishes from siblings like transcribe_from_url (for URL transcription) and get_transcript (for retrieving results), giving a clear purpose.

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 that this tool is for local files, but it does not explicitly state when to use it versus alternatives like transcribe_from_url. There is no mention of prerequisites, file size limits, or when not to use this tool.

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