sym_avatar_video

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

With no annotations provided, the description carries full behavioral burden. It discloses the synthesis pipeline (TTS, lip-sync, captions), key constraints (script length, speed range), default voice behavior, current credit cost, and the asynchronous jobId return pattern. This is comprehensive for a creation tool.

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?

The description is compact, front-loaded with purpose, then constraints and integration notes, with no filler words. Every sentence contributes to correct invocation.

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?

The core async workflow is explained (returns jobId, wait with sym_wait), but the nested items array can contain multiple video jobs, and parameters like dryRun, folder, prefix, volume, captions, and name are not addressed. For a tool with no output schema and rich input schema, this leaves notable gaps for an agent.

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 adds meaning for script (length limit, spoken language), voiceId (source from sym_voices, default avatar voice), and speed (0.8–1.3 range), but leaves items/avatarId/captions/folder/prefix/volume/dryRun unexplained. The description covers only a subset of the parameters, so it is adequate but incomplete.

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 creates a talking avatar video from a script, mentioning TTS, lip-sync, and captions. It is specific about the verb and resource, but it does not explicitly differentiate from sibling tools like sym_dub or sym_generate, so it misses the top bar for sibling distinction.

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 clear operational context: voiceId should come from sym_voices, defaults to the avatar's own voice, speed range 0.8–1.3, script limit of 1000 characters, and to wait with sym_wait after receiving jobId. However, it does not state when to choose this tool over alternatives or when not to use it.

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