hcloud_list_ssh_keys

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only that all SSH key objects are returned, without explaining pagination behavior, default auto-pagination, or filtering effects. With annotations carrying the main behavioral burden, this is adequate but thin.

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?

The description is very short and front-loaded with the core action. The second sentence, 'Returns all SSH key objects,' is somewhat redundant but does clarify the return scope. It avoids unnecessary text.

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 seven optional filtering and pagination parameters, and no output schema. The description says all SSH key objects are returned but does not mention filtering, sorting, or the auto-paginate default, leaving the agent to rely entirely on the schema. Annotations cover safety, but the description could do more for a list tool with this many optional parameters.

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 seven parameters are already documented in the input schema. The description adds no parameter semantics beyond saying all objects are returned. Baseline 3 is appropriate when the schema does the heavy lifting.

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: 'List SSH keys' and 'Returns all SSH key objects.' This clearly distinguishes it from mutating siblings such as hcloud_create_ssh_key or hcloud_delete_ssh_key. It does not explicitly differentiate from hcloud_get_ssh_key, but the list-vs-get distinction is clear enough.

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 description gives no guidance on when to use this tool versus hcloud_get_ssh_key or other list tools. It also does not mention whether filtering via the available schema parameters is expected. Usage is only implied by the word 'List'.

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