Generate a strong random password — handy when creating a user or setting a password on a server. Returns the password only; nothing is stored.
| Name | Required | Description | Default |
|---|---|---|---|
| length | No | length (default 20, 8-128) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already state readOnlyHint=true and idempotentHint=false, so the description doesn't need to re-cover safety. It adds valuable behavioral detail: 'Returns the password only; nothing is stored.' The description and annotations are consistent.
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?
Two short sentences with zero filler. The main purpose and key behavioral guarantee are front-loaded, and there's no extraneous detail.
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 one-parameter utility with annotations and no output schema, the description is complete: it states what the tool does, when to use it, what it returns, and the storage guarantee. Nothing essential is missing.
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 100%, and the single parameter length is already documented with default and range ('default 20, 8-128'). The description adds little beyond the schema, but for one simple parameter, that is acceptable.
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 states a precise verb ('Generate') and resource ('strong random password') and immediately explains the practical use case. The tool is clearly distinct from all siblings (hosts_list, sftp_list, etc.), so an agent can tell when to reach for it.
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 gives concrete contexts: 'handy when creating a user or setting a password on a server.' It doesn't explicitly say when not to use it or name an alternative, but given no sibling does anything similar, the usage context is strong enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool maps to a distinct action: password generation, host enumeration, SFTP file listing/reading/writing, and SSH command execution. Although sftp_read and ssh_exec could both be used to retrieve file contents, the descriptions explicitly separate them by file type and size.
Most tools follow a consistent <resource>_<verb> pattern: hosts_list, sftp_list, sftp_read, sftp_write, and ssh_exec. generate_password is the only outlier using <verb>_<noun>, but it is still clear, short, and doesn't cause real confusion.
Six tools is a tight, well-scoped set for managing remote servers via Termalin. Each tool covers a practical need without redundancy or feature bloat.
The main server-management workflow is covered: list hosts, execute commands, list files, read files, write files, and generate passwords. Minor gaps exist around SFTP operations like delete, move, rename, or create-directory, but these can be worked around with ssh_exec.