export_animation_frames

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

No annotations are supplied, so the description carries the entire behavioral burden. It reveals the output format and destination but omits important behavior: that it writes files (a mutation with side effects), what happens on filename collisions or to existing folder contents, whether the range is inclusive, and likely runtime cost for long ranges.

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 short sentence, front-loaded with the verb and the output artifact, with no filler. Nothing could be trimmed without losing content.

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 file-writing export tool with four undocumented parameters, no annotations, and no output schema, one sentence is far from sufficient. An agent cannot determine defaults behavior, range semantics, or overwrite risk before invoking it.

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; it only partially does. 'Numbered' hints that start/end select a frame range and 'workspace folder' maps to folder, but the meaning of start/end (frame indices, inclusive/exclusive, null = all frames) and the role of prefix are left entirely unexplained.

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 ('Render') plus the resource ('frames') and the output form ('numbered PNGs into a workspace folder'). It implicitly separates this from render_video or export_image by describing a sequential PNG frame dump, though it never names an alternative 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?

There is no when-to-use guidance: no mention of prerequisites (e.g., an animation/document must be active), no indication that leaving start/end null exports the whole timeline, and no pointer to export_image, render_video, or animation_contact_sheet as alternatives.

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