cloud_list_images

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

The description indicates a read-only operation ('list'), which is consistent with the typical behavior. However, no details are provided about pagination, filtering, or any other behaviors beyond the basic listing. Since no annotations are present, the description carries the full burden and is minimally informative.

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 very concise, using a single sentence with no verbose or redundant language. However, it sacrifices necessary detail. For conciseness alone, it earns a 4.

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's complexity (8 parameters, no schema descriptions, no annotations), the description is severely incomplete. It fails to cover pagination, filtering, or output structure, leaving the agent without essential context for correct usage.

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 schema has 8 parameters with 0% description coverage, and the tool description does not explain any of them. An agent cannot determine the purpose of 'page', 'per_page', 'type', etc., from the description alone. This is a critical gap.

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 tool lists images and enumerates the types (system, snapshot, backup, app). It distinguishes from sibling tools like cloud_get_image by specifying 'list', and from create/delete tools. However, it could be more explicit by mentioning it returns a collection.

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 cloud_get_image for specific images or cloud_create_server_image for creation. The description lacks any context on typical usage or prerequisites.

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