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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says a video will be generated; it does not mention that this is a media-creating operation with likely cost/time consequences, nor does it describe what the tool returns or whether generation is asynchronous. This is a meaningful transparency gap for a POST media generation 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?

A single, front-loaded sentence with no filler. It communicates the core action, the output type, the duration constraint, and the input requirement in minimal words.

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 tool is simple and the core information is present, but there is no output schema, no return-value description, and no mention of side effects or model selection context. An agent could call it correctly from the obvious parameters, but it would be guessing about what happens after the call.

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?

With 0% schema description coverage, the description must compensate for parameter meaning. It clarifies that 'prompt' is a text prompt and implies the duration range, but it leaves the 'model' parameter entirely unexplained beyond its default value in the schema. The added meaning is partial, not complete.

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 verb ('Generate'), a clear resource ('a short AI video'), and the input ('from a text prompt'). The 'short' qualifier plus the explicit '1-5 seconds' range distinguishes it from the sibling tools post_media_video_generate_medium and post_media_video_generate_long.

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?

The duration range '1-5 seconds' gives clear context for when this tool is appropriate, and the sibling tool names make the alternative durations inferable. It does not explicitly say 'use medium or long for longer videos,' but the boundary is effectively stated.

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