export_gif

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

No annotations, so the description carries the full burden. It does disclose one real behavioral trait: the operation can be blocked by unresolved error obligations, and it exports an existing render rather than re-rendering. It says nothing about permissions, output location, size limits, or whether the export is saved server-side or returned.

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?

One sentence, front-loaded with the action and result, with the blocking caveat confined to a parenthetical. Nothing is wasted, though the terseness comes at the cost of the missing parameter and output guidance.

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 explained, but the description fails to resolve the core ambiguity of two optional, zero-coverage identifier parameters and leaves 'open error obligations' undefined. For a tool whose inputs are mutually ambiguous, this is not enough to invoke it confidently.

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 0% and both parameters (scene_id, project_id) are optional and undocumented. The description never explains the relationship between the two identifiers, which one is needed, or whether both are required together, so the ambiguity an agent most needs resolved is left open.

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 and resource: exports the latest render of a scene as a GIF. The word 'latest render' implicitly distinguishes it from render_scene/render_frame, which produce renders rather than export them, though it never names those siblings explicitly.

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?

'Blocked by open error obligations' hints at a precondition, and 'latest render' implies a render must exist first, which is useful contextual guidance. However, there is no explicit statement of when to call this instead of render_scene/render_frame, and no mention of what to do if no render exists.

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