hcloud_get_image

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only that a specific Image object is returned, without disclosing error behavior (e.g., missing ID), authentication needs, or response characteristics; with no output schema, this is a notable 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?

It is short and front-loaded, but the second sentence ("Returns a specific Image object") is redundant with the first and adds almost no information. The definition is under-specified rather than verbose, making conciseness feel accidental.

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 get-by-ID tool, the definition enables invocation but not understanding of the result: there is no output schema, and the description does not explain what fields an Image object contains or what happens on a missing ID. The annotations cover safety, but the description is too thin to complete the tool's contract.

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 parameter is documented as "ID of the Image." The description adds no formatting or semantic detail beyond the schema, so the baseline of 3 applies when the schema fully carries parameter documentation.

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 verb and resource ("Get an Image") and adds that it returns "a specific Image object," which faintly distinguishes it from hcloud_list_images. However, it is largely a restatement of the tool name and does not mention lookup by ID or explicitly differentiate it from siblings such as hcloud_get_image_action.

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 use this tool versus alternatives like hcloud_list_images or hcloud_get_image_action. The description provides no prerequisites, no when-not conditions, and no routing to a sibling.

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