list_video_generations

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about pagination behavior (despite a cursor param), ordering, result limits, auth requirements, or what a response contains. The reference to the ElevenCreative API adds provenance but no operational context.

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 single sentence is front-loaded and free of padding, which is good, but its brevity comes at the cost of under-specification rather than efficiency. There is no structural element such as a usage clause or pagination note.

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?

With no annotations, no output schema, and two undocumented parameters, this is a thin listing tool whose definition covers only the bare minimum. An agent would have to guess how to page through results and how results differ from the several other list tools.

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% for both parameters, so the description would need to explain cursor and page_size semantics, and it explains neither. Default page size, cursor expiry, and the 1-100 bounds implicit in the schema are left entirely opaque.

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 and resource ("List video generations") plus the backing API, so the basic operation is unambiguous. It does nothing to distinguish this from siblings such as list_image_generations, list_generation_history, or list_generated_assets, so an agent cannot tell which listing to pick from the description alone.

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?

There is no guidance on when to use this versus the other listing tools, no mention of pagination walk order, and no prerequisites. The only hint about scope is the word "video" in the name.

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