list_image_generations

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

No annotations are provided, so the description carries the full behavioral burden and largely drops it. 'List' weakly implies a read-only paginated operation, but ordering, page size defaults, cursor expiry, and return shape are all unstated, and no output schema exists to fill the gap.

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 wasted clauses earns credit for terseness, but here brevity shades into under-specification rather than economy. The 'from the ElevenCreative API' tail is pure filler that could have been replaced by a useful clause about pagination.

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?

For a paginated listing endpoint with two undocumented parameters, no annotations, and no output schema, the description supplies neither the pagination contract nor the item shape. It is materially short of what an agent needs to invoke and interpret results correctly.

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?

Both parameters (cursor and page_size) have 0% schema description coverage, and the description says nothing about either. An agent learning how pagination works here — how the cursor is obtained, what page_size defaults to, the 1-100 bounds — gets no help from the text.

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 clear verb and resource (list image generations), so the basic action is unambiguous. However, it does nothing to separate this tool from close siblings such as get_image_generation, list_generated_assets, list_generation_history, and list_video_generations, and the trailing phrase 'from the ElevenCreative API' adds no distinguishing information.

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 call this instead of get_image_generation for a single item or list_generated_assets for a broader asset listing. The agent must infer usage purely from the tool name, with no exclusions or prerequisites stated.

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