generate_avatar_video

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states it 'generates' a video, without mentioning if the operation is synchronous or asynchronous, potential side effects, rate limits, or what happens with errors. This is insufficient for an AI agent to understand the tool's 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?

The description is extremely short (one sentence), but conciseness is not valuable when it omits critical information. It fails to convey key details about parameters, usage, or behavior.

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?

Given the tool has 4 parameters (3 required), no output schema, and no annotations, the description is completely inadequate. It provides no context about the return value, error handling, or how the video generation process works.

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?

The input schema has 0% description coverage, meaning none of the 4 parameters are described. The description adds no meaning beyond the schema—it only mentions the API name. The agent has no indication of what each parameter represents or its expected format.

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 action ('Generates') and the resource ('new avatar video') with the specific API (HeyGen). However, it does not differentiate from the sibling tool 'generate_avatar_video_with_multiple_scenes' beyond the name, leaving ambiguity about whether this tool supports only single scenes.

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?

No guidance is provided on when to use this tool versus alternatives like 'generate_avatar_video_with_multiple_scenes'. There is no mention of prerequisites, typical use cases, or required authentication context.

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