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

Goes well beyond the annotations: discloses that it spends credits (~50–200, dynamic by duration/type), names creditsReserved as the return field, explains the async pattern (jobId → poll get_job), states refunds on failure, and gives the UGC input precondition. Annotations only say destructive/non-idempotent/open-world; the description supplies the actionable behavior.

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?

Tight, front-loaded block: async nature, cost, return/poll, and UGC precondition are all in three compact sentences with zero filler. Credit cost and refund behavior are stated before the UGC caveat, matching importance order.

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 an 8-param async job tool with no output schema, the description covers what the agent needs: cost, async/polling follow-up, failure refund, and the input preconditions for UGC branches. Nothing essential is missing.

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 63%, so the schema documents topic, script, characterId, scenePrompt, durationSeconds. The description adds cross-cutting meaning the schema lacks: which videoTypes are UGC ('ugc','brainrot','ugc-broll','ugc-demo') and that those require characterId + script, plus where characterId comes from. Doesn't cover platform/additionalInstructions meaning, so not a 5.

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+resource ('kick off an ASYNC full video production job') and names the exact flow ('Quick Create'), distinguishing it from siblings like create_ai_edit, create_ai_story, or seedance_generate_video. An agent can pick this tool apart from the other ~70 creation/upload tools without opening the schema.

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?

Gives strong context: it's the Quick Create flow, UGC types require characterId + script (with pointers to list_characters/list_character_library). However it doesn't explicitly state when NOT to use it vs. its many sibling video-generation tools (create_ai_edit, seedance_generate_video, studio_generate_video), leaving routing inferred.

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