combell_ssh_keys_add

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

Annotations already indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is partially covered. The description adds the intended effect of enabling SSH/SFTP login, but does not disclose additional behavioral details such as duplicate-key handling, permissions required, or whether existing keys are preserved.

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, well-structured sentence that immediately states the action, target, and purpose. Every part earns its place, and there is no redundant or vague wording.

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 simple two-parameter operation with no output schema, the description conveys the action and outcome sufficiently for an agent to select and invoke the tool. It could have mentioned what happens to existing keys or whether duplicate keys cause errors, but annotations and schema cover the essential operational context.

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 schema already fully documents both parameters, including an example for public_key. The description adds little beyond restating that a public key is attached to a Linux hosting, so it matches the params but does not meaningfully supplement the schema's parameter descriptions.

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 specific verb ('Attach') with a clear resource ('SSH public key') and target ('Linux hosting'), and states the purpose ('so it can be used to log in over SSH/SFTP'). This clearly distinguishes it from sibling tools like combell_ssh_keys_list, combell_ssh_keys_delete, and combell_ssh_keys_list_all.

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 implies when to use the tool: when an SSH public key needs to be attached to a hosting account for SSH/SFTP access. However, it does not explicitly mention alternatives or exclusions, such as using combell_ssh_keys_list to view keys or combell_ssh_keys_delete to remove one.

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