hcloud_list_images

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds only the downstream-consumption context and says nothing about pagination behavior, default result size, or whether the list is region-scoped beyond the required parameter.

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 the resource first and the motivating use case second. No filler or redundant restatement of the tool name.

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 seven-parameter list tool with no output schema, the description does not indicate what fields come back (image IDs, names, status) or how results are ordered/limited, which matters since the stated goal is extracting an image_ref. Adequate but leaves a real gap for the caller.

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 100%, so all seven parameters (including the filter enums for status, os_type, imagetype, architecture) are already documented in the schema. The description adds no filtering semantics or format hints beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('List available IMS images') and adds the downstream purpose (finding image_ref for ECS/CCE/AS). It is clearly distinguishable from the sibling hcloud_show_image by the list-vs-show verb, though it never names that sibling explicitly.

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 parenthetical gives a concrete use case (locating image_ref before creating ECS/CCE/AS resources), which implies when to call it. However, there is no explicit guidance on when to prefer hcloud_show_image or hcloud_list_os_versions instead, so the agent must infer the boundary.

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