hcloud_show_image

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 contributes the returned attribute set (min_ram, min_disk, status), which is genuinely useful since there is no output schema, but it says nothing about error behavior for an invalid image_id or region scoping.

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 zero filler. The unexplained 'IMS' abbreviation and parenthetical field list are compact and readable.

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 two-parameter read tool with full schema coverage and annotations, this is nearly sufficient. The only real gap is that it does not explain where an image_id comes from or how region interacts with the lookup.

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%, but the schema field text is only a restatement ('Region', 'Image ID'), so no real meaning is added by either source. The description adds nothing about region format or ID format, 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 ('Get details') and resource ('IMS image') and names the fields returned. The word 'specific' plus the required image_id signals single-resource lookup versus the sibling hcloud_list_images, 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?

No when-to-use guidance, no mention of the list-first workflow to obtain an image_id, and no exclusions. The usage is only inferable from the tool name and the required image_id parameter.

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