List SSH Keys

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

No annotations are present, so the description carries the full burden. 'Get all SSH public keys' implies a read-only operation and clarifies the scope ('all'), but it discloses no other behavioral traits such as auth requirements, pagination, rate limits, or return format. It is adequate for a simple read operation but adds minimal value beyond the tool name.

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 a single, clear sentence with no extraneous words. It is front-loaded with the main verb and resource, making it highly scannable and efficient. Perfectly sized for a simple list operation.

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?

Given the tool's simplicity (zero parameters), the description covers the core purpose. However, there is no output schema, so the agent is left without hints about the response structure (e.g., array of objects with key IDs/fingerprints). This is a minor gap but does not compromise the basic understanding of the operation.

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?

The tool has zero parameters, and the schema description coverage is trivially 100%. Per the baseline rule for 0-parameter tools, the description does not need to explain parameters. It correctly omits any parameter information, and the schema already communicates that no arguments are required.

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 'Get all SSH public keys' uses a specific verb ('Get') and resource ('SSH public keys'), clearly indicating a read/list operation. It effectively distinguishes itself from sibling tools like vps_keys_create, vps_keys_delete, and vps_keys_attach, and even clarifies that it returns public keys specifically.

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 provides no guidance on when to use this tool versus alternatives. With siblings like vps_get_attached_keys (which lists keys attached to a VPS) and vps_keys_create, the agent would benefit from explicit context, but none is provided. There is no mention of exclusions or alternative tool references.

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