hcloud_list_os_versions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety and idempotency are covered. The word 'available' hints results are filtered by region, but the description adds little beyond the annotations and does not describe return volume or ordering.

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 short sentence with the purpose front-loaded and no wasted words. Its brevity is appropriate for a one-parameter list tool, though it borders on terse.

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 simple read-only list tool with full schema coverage and annotations carrying the safety profile, the description is minimally sufficient. It leaves out whether results are scoped per region or what the entries look like, which would help an agent construct image selection follow-ups.

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 coverage is 100% and the single 'region' parameter is documented in the schema, so the baseline is 3. The description adds no format or constraint detail about region beyond what the schema already provides.

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 OS versions. The parenthetical 'key for image selection' clarifies what the returned versions are used for, distinguishing it from generic image listing siblings like hcloud_list_images. It does not explicitly name a sibling it is not, but the resource naming is specific enough to disambiguate.

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 'key for image selection' implies the context in which to call it (when choosing an image/OS), but there is no explicit when-to-use versus alternatives guidance, no prerequisite statement, and no note about when to prefer hcloud_list_images instead.

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