export_animation_gif

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

With no annotations, the description carries the full burden. It does disclose a meaningful behavioral trait ('preserving frames'), indicating that multi-frame inputs are retained. However, it omits other critical behaviors: whether the input file is read without modification, what happens on output file conflicts, and the exact meaning of 'animated image' (e.g., APNG, WebP, GIF). The 'preserving frames' disclosure earns a 3, but the gaps prevent a higher score.

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. The core action, input scope, and output format are presented first, and the crucial 'preserving frames' behavior is included. All content is relevant and efficiently ordered.

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?

For a tool with no annotations, no output schema, and no parameter descriptions, the one-line description is insufficient. It doesn't clarify prerequisites (e.g., input file must exist), side effects (creating/overwriting a file), or how it differs from the many sibling export/convert tools. An agent would need to inspect other tools or experiment to use it correctly.

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% and the description adds no parameter-level meaning. It never mentions that the parameters are file paths, what formats they should be, or how they map to the conversion. The bare parameter names in the schema are all an agent has, so the description fails to compensate.

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 ('convert'), the resource type ('PNG, GIF, or animated image'), and the output format ('GIF'), with the distinguishing detail 'preserving frames' that separates it from siblings like export_sprite or export_frame. An agent can clearly tell this tool produces a GIF from an existing image or animation.

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 is provided on when to choose this tool over alternatives such as export_spritesheet, export_frame, or convert_animation_to_pixel_art. The description gives the 'what' but not the 'when' or 'when-not', leaving the agent to infer usage from the name and context.

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