hcloud_get_image_action

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds the deprecation status, which is genuine extra context, but omits that the action must belong to the given image and says nothing about the 'wait' polling behavior exposed by the schema.

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?

Short and front-loaded, with the deprecation callout before the functional sentence. The opening heading and the closing sentence restate the same fact ('Get an Action for an Image' / 'Returns a specific Action for an Image'), which is mild redundancy but not harmful.

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 3-parameter read tool with full annotations, no output schema, and a schema that documents every field, only light prose is needed. A hint about what an Action object contains or when a 404 occurs would help, but nothing essential to correct invocation is missing given the deprecation warning is present.

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 id, action_id, and wait are all documented upstream; baseline 3 applies. The description adds no semantics about the id/action_id pairing or what polling means for a read call beyond what the schema states.

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 ('Returns a specific Action for an Image'), which is unambiguous. It does not distinguish itself from nearby siblings such as hcloud_get_action, hcloud_get_images_actions_id, or hcloud_list_image_actions, so an agent still has to infer which retrieval shape to pick.

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 deprecated notice and changelog link effectively say 'prefer something else,' which is useful when-not-to-use signal. However, it never names the replacement endpoint, so the agent knows to avoid this tool but not what to call instead.

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