hcloud_list_server_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 that sort and status narrow the result set, but says nothing about pagination behavior, the auto_paginate soft-cap merging, or result volume — and "Returns all Action objects" is mildly at odds with the per_page default of 25 that the schema exposes.

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 with the resource scope front-loaded and no filler. The first line slightly restates the title before the more informative second sentence, which is the only inefficiency.

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 read-only listing tool with full schema coverage and annotations, the description is minimally sufficient. It omits any characterization of the returned Action objects and pagination semantics, and provides no sibling disambiguation despite an extremely crowded action-listing namespace.

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 parameters are fully documented in the schema and baseline 3 applies. The description only echoes `sort` and `status` and adds no semantics for `id`, `page`, `per_page`, or the non-obvious `auto_paginate` flag.

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 ("List Actions for a Server") and scopes it to a single server via the required `id`. It does not distinguish itself from the many action-listing siblings such as hcloud_get_servers_actions (multi-server) or hcloud_list_actions (global), which an agent could easily confuse with this one.

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 by the name and the mention of sort/status. There is no statement of when to prefer this over hcloud_get_servers_actions, hcloud_list_actions, or hcloud_get_server_action, and no prerequisites or exclusions are given.

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