hcloud_list_image_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 safety is covered. The description adds only that results are sortable and status-filterable, both of which are restated from the schema, and says nothing about pagination behavior or the default auto_paginate soft-cap merge.

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 the resource scope. No filler, though the second sentence merely repeats schema facts rather than earning its place.

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?

A read-only paginated list endpoint with 100% schema coverage and annotations covering safety: nothing further is required for an agent to invoke it correctly. Return values are self-evident from 'Action objects' and no output schema is needed.

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 all six params (id, page, per_page, sort, status, auto_paginate) are already documented in the schema. The description mentions only `sort` and `status` and calls them 'URI parameters', which adds nothing beyond the schema and slights the image `id` that drives the call.

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?

Specific verb+resource: lists Action objects scoped to a single Image (required `id`). The phrase 'for an Image' implicitly separates it from hcloud_get_images_actions (all images) and hcloud_get_image_action (single action), but neither sibling is named.

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?

Usage is only implied: you need an Image ID to poll its async action history. There is no explicit when-to-use statement, no mention of choosing between this and hcloud_get_images_actions or hcloud_list_actions, and no guidance on polling for completion versus hcloud_wait_action.

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