hcloud_update_ssh_key

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

Annotations declare destructiveHint=true and openWorldHint=true, but the description adds no behavioral context beyond 'updates'. It omits that the supplied labels set fully replaces the existing labels – critical information for an agent deciding whether this call destroys state – leaving only the nested schema to convey it.

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?

Very short, but the title line and the body sentence are near-verbatim repeats ('Update an SSH key' / 'Updates an SSH key'), so half the text is redundant filler rather than new information.

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 mutation with a nested body object, no output schema, and no annotation elaboration, the description leaves out the label-replacement side effect, required id semantics, and what happens to fields not supplied – too much 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 coverage is 50%; the description names the two mutable body fields (name, labels) and so roughly mirrors what the schema documents, but it adds nothing about the id requirement, label overwrite semantics, or immutable fields.

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 ('Update an SSH key') and names the two mutable fields (name, labels), which distinguishes it from the get/list/create/delete siblings sharing the same resource.

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?

No guidance on when to use this versus hcloud_create_ssh_key, hcloud_delete_ssh_key, or the other update_* tools, and no prerequisites or caveats about what an update affects.

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