hcloud_list_actions

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

Annotations already establish that this is a read-only, non-destructive operation. The description adds useful behavioral context by disclosing that the old list-all behavior was removed in January 2025, preventing a critical misuse. It does not mention authentication needs, rate limits, or pagination behavior despite the auto_paginate parameter.

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?

The description is front-loaded with the core action and is mostly efficient. The deprecation note is valuable, though the two changelog URLs are more verbose than strictly necessary for an agent to invoke the tool correctly.

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 read-only tool with full schema coverage and annotations covering safety, the description is complete enough to call correctly: it makes clear that IDs are required and that listing all actions is no longer supported. It could be slightly more complete by routing among the many action-related siblings.

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 the `id` and `auto_paginate` parameters in detail. The description restates that actions are specified by `id` but adds no meaning beyond what the schema provides, making the baseline 3 appropriate.

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 uses a specific verb and resource: 'Get multiple Actions' and 'Returns multiple Action objects specified by the `id` parameter.' It clearly scopes the operation to IDs rather than listing everything, but it does not explicitly distinguish itself from sibling tools like hcloud_get_action or the resource-specific list_*_actions tools.

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 implied by the requirement to supply IDs and by the note that listing all actions was deprecated and removed. However, the description does not explicitly state when to use this tool versus hcloud_get_action for a single ID or hcloud_list_server_actions for server-scoped actions, nor does it name alternatives.

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