Create SSH Key

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Upload a new SSH public key' without explaining validation, duplicate handling, or whether the key is associated with a VPS. This is minimal for a mutating operation.

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, front-loaded sentence with no filler words. It is appropriately concise for a simple create operation, though it could be expanded with usage context without becoming overly long.

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 low-complexity with two required parameters and no output schema, so the description is minimally adequate. However, it lacks context about the purpose of the key in the VPS ecosystem, naming constraints, or expected return value, making it incomplete in isolation.

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 input schema already provides 100% coverage with clear descriptions for both 'name' and 'key'. The description adds no additional parameter details, so it neither enhances nor detracts from the schema-provided semantics.

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 uses 'Upload' as a specific verb and 'SSH public key' as the resource, clearly indicating a creation action. The word 'new' helps distinguish from listing or deleting, though it does not explicitly reference sibling tools like vps_keys_attach.

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 vs. alternatives such as attaching an existing key, listing keys, or deleting keys. The description does not mention prerequisites or scenarios where this tool is appropriate, leaving the agent to infer usage from the tool name.

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