create_ssh_key

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

The description adds useful behavior beyond the annotations: confirm=true is mandatory, and ssh_key must be public key material, never a private key. Given the annotations only provide common mutation flags, this is meaningful context, though it stops short of discussing auth, rate limits, or result behavior.

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 compact and front-loaded: purpose first, usage connection second, then critical parameter constraints. Every sentence adds necessary value with no filler.

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 3-parameter mutation tool with no output schema, the description gives enough orientation to use it safely: purpose, connection to create_vps, confirm requirement, and key material type. It does not mention return values, but this is not a major omission for such a focused tool.

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?

With 0% schema description coverage, the description compensates by explaining a key fact for two of the three parameters: ssh_key must be public key material and confirm must be true. The title parameter is not described, leaving a gap, but the most safety/problem-prone parameters are clarified.

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 a clear action verb ('Save') with a specific resource ('SSH public key to this account') and connects it to a concrete use case ('installing onto future VPS instances via create_vps's own ssh_key parameter'). This distinguishes it from sibling tools like list_ssh_keys and delete_ssh_key.

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 states exactly when the tool is relevant: when the agent needs to store an SSH key for later use with create_vps. It also gives a clear precondition ('Requires confirm=true'). It does not explicitly name alternatives/exclusions, but the use case is specific enough to guide selection.

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