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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says a video is generated from a text prompt and gives a duration range; it does not mention output format, whether generation is asynchronous, model behavior, or other side effects an agent should expect.

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 a single, front-loaded sentence with no filler. It is concise and readable, though the brevity comes at the cost of omitting important differentiators and parameter details.

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 there is no output schema, no annotations, and zero parameter descriptions, this description is not complete enough for reliable tool selection and invocation. It lacks output expectations, sibling differentiation, and model/duration semantics beyond the raw schema.

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 for undocumented parameters. It only clarifies that 'prompt' is a text prompt; 'model' and 'duration_seconds' are left to their schema names and constraints, and no additional meaning or examples are provided.

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 states a specific action, 'Generate a short AI video', and gives an explicit 6-10 second duration range, so the core purpose is clear. However, it does not distinguish this medium variant from the sibling short/long video tools, and calling a 'medium' tool 'short' is somewhat confusing.

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 given about when to use this tool versus post_media_video_generate_short or post_media_video_generate_long. The presence of short/long siblings makes this gap significant; an agent must guess how durations map across the three tools.

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