hcloud_get_certificate_action

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 lifecycle context (deprecation) and a functional restriction (managed-only actions) that annotations do not carry. It does not describe what an Action object contains or how the `wait` polling behaves on failure.

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?

Three short, front-loaded blocks: the deprecation warning leads, then the purpose sentence, then the scope caveat. No filler; a reader can stop after the first line if deprecation is disqualifying.

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?

The tool has no output schema, so the description should say anything about the returned Action (fields, status values, terminal states) but says nothing. Given the deprecation and managed-only caveats are present, it is adequate but leaves a real gap for a read tool whose return value is undefined.

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 three parameters (id, action_id, wait) are already documented in the schema; baseline 3 applies. The description adds only the indirect constraint that `id` must reference a managed Certificate, no syntax or format detail beyond the schema.

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: 'Returns a specific Action for a Certificate', and adds a meaningful scope constraint that only `managed` Certificates have Actions. It does not distinguish itself from the near-duplicate sibling hcloud_get_certificates_actions_id, leaving the agent to guess between them.

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?

The Deprecated banner with a changelog link is an explicit 'do not use / migrate away' signal, and the managed-only note tells the agent when the call will yield nothing. It stops short of naming the replacement endpoint or sibling tool, so routing is implied rather than explicit.

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