hcloud_get_images_actions

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond restating the sort/status/id parameters from the schema, and critically leaves unresolved whether the result set is scoped to an image or global — the single most consequential behavioral question here.

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?

Two short sentences, front-loaded with the operation and followed by the filtering note. No wasted text, though the filtering sentence largely duplicates structured schema content rather than carrying new information.

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?

With full schema coverage, annotations, and no output schema, the mechanics are adequately covered. But for a tool whose name suggests image scoping and whose description says 'all actions', the description should resolve that scope question — and does not.

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 the schema already documents page, per_page, sort, status, and id thoroughly. The description merely names sort/status/id, adding no format, default, or interaction semantics beyond the schema — baseline 3.

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?

It says "List Actions" and "Returns all Action objects", which gives a verb and a resource, but the tool name (hcloud_get_images_actions) implies image-scoped actions while the description claims it returns ALL actions. An agent cannot tell whether this is scoped to images or global, and the description never differentiates it from hcloud_list_actions or hcloud_get_images_actions_id.

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 prerequisites, and no mention of the obvious siblings (hcloud_list_actions, hcloud_get_action, hcloud_get_images_actions_id). The only usage hint is how to sort and filter, which is invocation mechanics rather than selection guidance.

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