hcloud_list_keypairs

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond them – no note on pagination, whether all key pairs are returned regardless of region scoping, or result ordering.

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 words with zero padding, so nothing is wasted. However, brevity crosses into under-specification for a cloud API tool, leaving no room for the context a caller would want; it is efficient but thin.

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 is simple – one required string parameter, no output schema, and annotations covering its read-only nature – so the minimal description is not crippling. Still, the meaning of 'region' and the scope of results are left unstated, which is a real gap for an open-world listing call.

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 100%, but the sole parameter's schema description is just "Region", which is nearly as terse as the tool description. The description does not compensate by explaining whether region filters results or is only a routing/endpoint selector. Per the high-coverage baseline, 3 is the appropriate ceiling here.

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?

"List SSH key pairs" gives a specific verb (list) and a specific resource (SSH key pairs), so the agent knows exactly what the tool returns. Differentiation from siblings is unnecessary here since no other sibling deals with key pairs, though the description itself does no explicit routing.

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 use this tool versus alternatives, no prerequisites, and no exclusions. The only implied usage is the generic 'list a collection', which the agent must infer from the verb alone.

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