export_gif

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

No annotations are provided, so the description carries the full burden. It does not say that the call writes a file to disk, whether an existing file at the destination is overwritten, whether conversion is slow or resource-intensive, or what happens if the recording is still in progress — all material for a side-effecting 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?

A single front-loaded sentence with no filler, expressing action and result compactly. However, that brevity leaves no room for the prerequisite and parameter detail the tool actually needs.

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?

An output schema exists, so return values need not be spelled out. But for a file-producing tool with zero annotation coverage and three undocumented parameters, the description omits essential context: preconditions, output location semantics, and the quality/size tradeoff.

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% across three parameters, and the description names none of them. The purpose of `output` (destination path vs. directory) and the tradeoff controlled by `high_quality` (quality vs. file size) are completely undocumented, as is the expected form of `recording_id`.

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?

States a specific verb (convert) and resource (a recording → animated GIF), which clearly separates it from the recording-lifecycle siblings like trim_recording or start_recording. It doesn't explicitly name a sibling or contrast with one, so it stops short of 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?

There is no statement of when to use this tool, no prerequisites (e.g., whether the recording must be stopped or trimmed first), and no alternatives mentioned. The only usage signal is the required recording_id, which the agent must infer from the schema.

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