Export

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is partly covered. However, the description adds no behavioral context such as whether it writes a file, returns exported content, requires a completed transcription, or supports specific output destinations. For an export operation with a free-form result object, this is a significant gap.

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 a single short sentence with no wasted words and is front-loaded. It is appropriately sized, though its brevity comes at the cost of detail rather than being a model of efficient completeness.

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 two required parameters, a nested 'result' object, no output schema, and only partial annotations, the description is too thin. It omits supported formats, expected result structure, output behavior, and distinctions from sibling transcription tools.

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 0%, so the description must compensate but does not. It only vaguely references 'formats' and says nothing about the required 'result' object or accepted format values, leaving both required parameters largely undocumented.

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 ('Export transcription') and distinguishes it from transcription and streaming siblings. It is clear what the tool does at a high level, though 'specified formats' leaves the supported formats unspecified.

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?

There is no guidance on when to use this tool versus siblings like transcribe_audio or audio_transcriber_save_stream, nor any mention of prerequisites or alternative workflows. The agent must infer the correct usage context.

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