hcloud_delete_ssh_key

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the danger profile is known. The phrase "It cannot be used anymore" adds a small amount of post-condition context, but the description never says the deletion is irreversible, what happens to servers currently referencing the key, or what errors can occur.

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?

It is short and front-loaded, but the second sentence restates the first ("Delete" / "Deletes") and the only new information is the trailing consequence clause. Wasted duplication in a four-word description is a real cost.

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 destructive single-parameter operation, annotations and the schema cover safety and input, so the description is minimally sufficient. It still omits the operational consequences an agent would want before calling a delete: irreversibility, in-use constraints, and error conditions.

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?

Only one parameter exists and schema coverage is 100%, with the schema already documenting `id` as "ID of the SSH Key" plus type and bounds. The description adds nothing about the identifier, which is acceptable given the schema does the work, but it is baseline rather than additive.

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 states a specific verb and resource ("Delete an SSH key") and the tool name already separates it from create/update/get/list siblings. However, it offers no explicit differentiation text, and the second sentence largely repeats the first rather than sharpening scope.

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?

There is no guidance on when to delete versus update, rotate, or detach a key, and no prerequisites such as whether the key must be unused by any server first. The agent must infer all of this from the tool name alone.

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