Deploy SSH key to a host

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

Annotations already convey that this operation is a mutation (readOnlyHint=false, idempotentHint=false), and the description adds that the write targets the host's authorized_keys file. However, it does not disclose important behavioral details such as whether the key is appended or overwrites existing keys, or whether it may require elevated permissions on the host.

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 short and front-loaded, with the main action in the first clause. The minor redundancy is that the first sentence nearly repeats the title, though it remains concise and readable.

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 state-changing tool with two undocumented parameters and no output schema, the description is too thin. It omits parameter semantics, behavior on repeated runs, authentication expectations, and what a successful deployment looks like.

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 0%, and the description does not explain what 'id' refers to or how it relates to 'targetHostId'. It only loosely implies the target host via 'target host' but leaves the primary 'id' parameter ambiguous, which is insufficient for correct invocation.

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 clearly states a specific verb and resource: it deploys an SSH public key to a target host's authorized_keys file. This makes the tool's purpose obvious, though it does not explicitly distinguish itself from sibling tools like termix_credentials_apply_credential_host.

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 versus alternatives, nor any exclusions or prerequisites. An agent gets only the verb 'deploy' to infer intent, with no context about when credential creation or applying a credential to a host would be more appropriate.

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