daz_render_animation_async

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

With no annotations, description discloses key behaviors: async, immediate return, request_id, and image sequence. Lacks depth on error handling, cancellation, or scene state impact.

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?

Brief paragraph with bulleted Args and return example. Front-loaded main action. No wasted words.

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?

Covers async workflow, monitoring tools, and return format. Missing cancellation hint (daz_cancel_request). Adequate for the complexity level.

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%, but description explains all 5 parameters with defaults for start_frame, end_frame, filename_pattern, camera, and consistent info for output_dir. Adds value beyond schema.

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?

Description clearly states it starts an animation render asynchronously and returns a request_id. It distinguishes from siblings like daz_render_animation (sync) and daz_render_async (single frame) by specifying it queues all frames as an image sequence.

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?

Explicitly mentions the async nature, long duration, and use of daz_get_request_status and daz_get_request_result for monitoring. Does not compare directly to alternatives but context implies when to choose async over sync.

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