hcloud_list_certificate_actions

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the managed-vs-uploaded constraint and what the `actions` key contains in the empty case. It does not describe pagination or default ordering behavior, which keeps it below a 5.

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 opening line states the operation up front, followed by return content, filtering notes, and the key constraint. There is minor redundancy between the first line and 'Returns all Action objects for a Certificate', but no sentence is wasted.

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 no output schema, the description must convey return shape, and it does: all Action objects for the certificate, with an explicit note that the `actions` array is empty for uploaded certificates. For a read-only list tool with fully documented parameters, this is nearly complete; only ordering/pagination behavior is left implicit.

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 fully documents id, page, sort, status, per_page, and auto_paginate — baseline 3 applies. The description reinforces that `sort` and `status` exist but adds no syntax or semantics beyond what the schema's enums and descriptions already provide.

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 ('List Actions for a Certificate', 'Returns all Action objects for a Certificate'), making the operation unambiguous. It does not explicitly distinguish itself from near-duplicate siblings such as hcloud_get_certificate_action (single action) or hcloud_get_certificates_actions, leaving that separation to inference.

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?

It gives clear usage context and a meaningful exclusion: only `managed` certificates have actions, while `uploaded` ones always return an empty array — an agent can use this to avoid a pointless call. It stops short of naming alternative tools for the single-action or account-wide cases, which is the only gap.

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