Export Media Transcript

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

Annotations indicate readOnlyHint=false, so it is not read-only, but no further behavioral details are given. It does not disclose whether the export is synchronous or asynchronous, what permissions are needed, or how the output is returned (e.g., download URL, binary). The description adds no behavioral context beyond the basic action.

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 concise sentence that effectively communicates the core purpose. It is front-loaded and avoids unnecessary words. However, it could be slightly more structured by listing formats more accurately.

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 tool has 8 parameters and an output schema, the description is too brief. It omits information about redaction, timestamps, speaker details, and output format. The output schema is not mentioned, leaving the agent unaware of what the tool returns.

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?

All parameters have descriptions in the schema (100% coverage), so the baseline is 3. The tool description adds context by mentioning 'transcript or insights' and listing some formats, but the enum has many more formats, potentially causing mismatch. The description does not explain the purpose of boolean flags like isRedacted or isTimeStamps.

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 exports a media file's transcript or insights in various formats. It distinguishes itself from sibling export tools like export_chat_answer and export_multiple_media by specifying it works on a single media file. However, the listed formats are a subset of the actual enum, which might cause slight confusion.

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?

No guidance on when to use this tool versus alternatives such as export_multiple_media. It does not mention prerequisites or use cases. The description only states what it does, not when to choose it.

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