animate_object

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

No annotations provided, so description carries full burden. Discloses mode defaults and quality difference, interpolation support, and dependency on object creation tools. Lacks details on credit consumption, job polling, or error behavior, but covers essential behavioral traits.

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?

Three sentences, front-loads the action, then adds mode and constraint details. No wasted words; every sentence earns its place.

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?

Description is brief given complexity (11 params, nested objects, no output schema). Doesn't explain result format (likely a job ID) or failure cases. Schema descriptions fill some gaps, but overall completeness is adequate but not thorough.

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 100%, baseline 3. The description adds value by explaining mode differences and direction rules beyond schema descriptions (e.g., 'v3 (default, higher quality, supports custom_start_frame/end_frame interpolation)'). This clarifies parameter context.

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 clearly states the tool animates a saved object by ID, specifies modes ('v3' vs 'pro'), and distinguishes from siblings by focusing on objects versus characters or text. The verb 'Animate' and resource 'SAVED object by ID' are specific.

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?

Provides explicit guidance: 'Do NOT pass directions for 1-direction objects; for 8-direction objects pass the directions' and 'Requires an object_id from create_object_1dir/8dir'. This helps the agent decide when to use it and prerequisites, but doesn't explicitly compare to sibling animation tools for characters.

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