hcloud_create_ssh_key

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful lifecycle note that the key becomes reusable by other calls, but says nothing about name uniqueness/conflict behavior, whether labels are persisted, or what the mutation returns.

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 action; the restated title line is mild redundancy but nothing is padded. It earns most of its space.

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?

There is no output schema and no annotations gaps to fill, so the description should explain the mutation's outcome and payload shape. It covers the lifecycle but omits response contents, label handling and duplicate-name behavior for a nested-object mutation tool.

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 reported as 0%, and the payload is a nested 'body' wrapper, so the description must carry the load. It names only 'name' and 'public_key', adds no format expectations for the public key (e.g. ssh-rsa/ed25519 prefixes) and ignores the 'labels' field entirely.

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 ('Create an SSH key') and names the two required fields. It is distinguishable from hcloud_delete_ssh_key and hcloud_update_ssh_key by the verb, but it never explicitly references siblings or scope (project-wide vs. per-key uniqueness).

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 sentence 'Once an SSH key is created, it can be used in other calls such as creating Servers' gives downstream context and implies when to call it. There is no explicit when-not guidance, no prerequisites, and no mention of how this differs from hcloud_list_ssh_keys or hcloud_get_ssh_key.

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